Action execution based on user modified hypothesis

ABSTRACT

A computationally implemented method includes, but is not limited to: presenting to a user a hypothesis identifying at least a relationship between a first event type and a second event type; receiving from the user one or more modifications to modify the hypothesis; and executing one or more actions based, at least in part, on a modified hypothesis resulting, at least in part, from the reception of the one or more modifications. In addition to the foregoing, other method aspects are described in the claims, drawings, and text forming a part of the present disclosure.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is related to and claims the benefit of theearliest available effective filing date(s) from the following listedapplication(s) (the “Related Applications”) (e.g., claims earliestavailable priority dates for other than provisional patent applicationsor claims benefits under 35 USC §119(e) for provisional patentapplications, for any and all parent, grandparent, great-grandparent,etc. applications of the Related Application(s)). All subject matter ofthe Related Applications and of any and all parent, grandparent,great-grandparent, etc. applications of the Related Applications isincorporated herein by reference to the extent such subject matter isnot inconsistent herewith.

RELATED APPLICATIONS

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/313,659, entitled CORRELATING SUBJECTIVE USERSTATES WITH OBJECTIVE OCCURRENCES ASSOCIATED WITH A USER, naming ShawnP. Firminger, Jason Garms, Edward K. Y. Jung, Chris D. Karkanias, EricC. Leuthardt, Royce A. Levien, Robert W. Lord, Mark A. Malamud, John D.Rinaldo, Jr., Clarence T. Tegreene, Kristin M. Tolle, and Lowell L.Wood, Jr., as inventors, filed 21 Nov. 2008, which is currentlyco-pending, or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/315,083, entitled CORRELATING SUBJECTIVE USERSTATES WITH OBJECTIVE OCCURRENCES ASSOCIATED WITH A USER, naming ShawnP. Firminger, Jason Garms, Edward K. Y. Jung, Chris D. Karkanias, EricC. Leuthardt, Royce A. Levien, Robert W. Lord, Mark A. Malamud, John D.Rinaldo, Jr., Clarence T. Tegreene, Kristin M. Tolle, and Lowell L.Wood, Jr., as inventors, filed 26 Nov. 2008, which is currentlyco-pending, or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/319,135, entitled CORRELATING DATA INDICATING ATLEAST ONE SUBJECTIVE USER STATE WITH DATA INDICATING AT LEAST ONEOBJECTIVE OCCURRENCE ASSOCIATED WITH A USER, naming Shawn P. Firminger;Jason Garms; Edward K. Y. Jung; Chris D. Karkanias; Eric C. Leuthardt;Royce A. Levien; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.;Clarence T. Tegreene; Kristin M. Tolle; Lowell L. Wood, Jr. asinventors, filed 31 Dec. 2008, which is currently co-pending, or is anapplication of which a currently co-pending application is entitled tothe benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/319,134, entitled CORRELATING DATA INDICATING ATLEAST ONE SUBJECTIVE USER STATE WITH DATA INDICATING AT LEAST ONEOBJECTIVE OCCURRENCE ASSOCIATED WITH A USER, naming Shawn P. Firminger;Jason Garms; Edward K. Y. Jung; Chris D. Karkanias; Eric C. Leuthardt;Royce A. Levien; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.;Clarence T. Tegreene; Kristin M. Tolle; Lowell L. Wood, Jr. asinventors, filed 31 Dec. 2008, which is currently co-pending, or is anapplication of which a currently co-pending application is entitled tothe benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/378,162, entitled SOLICITING DATA INDICATING ATLEAST ONE OBJECTIVE OCCURRENCE IN RESPONSE TO ACQUISITION OF DATAINDICATING AT LEAST ONE SUBJECTIVE USER STATE, naming Shawn P.Firminger; Jason Garms; Edward K. Y. Jung; Chris D. Karkanias; Eric C.Leuthardt; Royce A. Levien; Robert W. Lord; Mark A. Malamud; John D.Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle; Lowell L. Wood,Jr. as inventors, filed 9 Feb. 2009, which is currently co-pending, oris an application of which a currently co-pending application isentitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/378,288, entitled SOLICITING DATA INDICATING ATLEAST ONE OBJECTIVE OCCURRENCE IN RESPONSE TO ACQUISITION OF DATAINDICATING AT LEAST ONE SUBJECTIVE USER STATE, naming Shawn P.Firminger; Jason Garms; Edward K. Y. Jung; Chris D. Karkanias; Eric C.Leuthardt; Royce A. Levien; Robert W. Lord; Mark A. Malamud; John D.Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle; Lowell L. Wood,Jr. as inventors, filed 11 Feb. 2009, which is currently co-pending, oris an application of which a currently co-pending application isentitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/380,409, entitled SOLICITING DATA INDICATING ATLEAST ONE SUBJECTIVE USER STATE IN RESPONSE TO ACQUISITION OF DATAINDICATING AT LEAST ONE OBJECTIVE OCCURRENCE, naming Shawn P. Firminger;Jason Garms; Edward K. Y. Jung; Chris D. Karkanias; Eric C. Leuthardt;Royce A. Levien; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.;Clarence T. Tegreene; Kristin M. Tolle; Lowell L. Wood, Jr. asinventors, filed 25 Feb. 2009, which is currently co-pending, or is anapplication of which a currently co-pending application is entitled tothe benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/380,573, entitled SOLICITING DATA INDICATING ATLEAST ONE SUBJECTIVE USER STATE IN RESPONSE TO ACQUISITION OF DATAINDICATING AT LEAST ONE OBJECTIVE OCCURRENCE, naming Shawn P. Firminger;Jason Garms; Edward K. Y. Jung; Chris D. Karkanias; Eric C. Leuthardt;Royce A. Levien; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.;Clarence T. Tegreene; Kristin M. Tolle; Lowell L. Wood, Jr. asinventors, filed 26 Feb. 2009, which is currently co-pending, or is anapplication of which a currently co-pending application is entitled tothe benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/383,581, entitled CORRELATING DATA INDICATINGSUBJECTIVE USER STATES ASSOCIATED WITH MULTIPLE USERS WITH DATAINDICATING OBJECTIVE OCCURRENCES, naming Shawn P. Firminger, JasonGarms, Edward K. Y. Jung, Chris D. Karkanias, Eric C. Leuthardt, RoyceA. Levien, Robert W. Lord, Mark A. Malamud, John D. Rinaldo, Jr.,Clarence T. Tegreene, Kristin M. Tolle, and Lowell L. Wood, Jr., asinventors, filed 24 Mar. 2009, which is currently co-pending, or is anapplication of which a currently co-pending application is entitled tothe benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/383,817, entitled CORRELATING DATA INDICATINGSUBJECTIVE USER STATES ASSOCIATED WITH MULTIPLE USERS WITH DATAINDICATING OBJECTIVE OCCURRENCES, naming Shawn P. Firminger, JasonGarms, Edward K. Y. Jung, Chris D. Karkanias, Eric C. Leuthardt, RoyceA. Levien, Robert W. Lord, Mark A. Malamud, John D. Rinaldo, Jr.,Clarence T. Tegreene, Kristin M. Tolle, and Lowell L. Wood, Jr., asinventors, filed 25 Mar. 2009, which is currently co-pending, or is anapplication of which a currently co-pending application is entitled tothe benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/384,660, entitled HYPOTHESIS BASED SOLICITATIONOF DATA INDICATING AT LEAST ONE SUBJECTIVE USER STATE, naming Shawn P.Firminger, Jason Garms, Edward K. Y. Jung, Chris D. Karkanias, Eric C.Leuthardt, Royce A. Levien, Robert W. Lord, Mark A. Malamud, John D.Rinaldo, Jr., Clarence T. Tegreene, Kristin M. Tolle, and Lowell L.Wood, Jr., as inventors, filed 6 Apr. 2009, which is currentlyco-pending, or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/384,779, entitled HYPOTHESIS BASED SOLICITATIONOF DATA INDICATING AT LEAST ONE SUBJECTIVE USER STATE, naming Shawn P.Firminger, Jason Garms, Edward K. Y. Jung, Chris D. Karkanias, Eric C.Leuthardt, Royce A. Levien, Robert W. Lord, Mark A. Malamud, John D.Rinaldo, Jr., Clarence T. Tegreene, Kristin M. Tolle, and Lowell L.Wood, Jr., as inventors, filed 7 Apr. 2009, which is currentlyco-pending, or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/387,487, entitled HYPOTHESIS BASED SOLICITATIONOF DATA INDICATING AT LEAST ONE OBJECTIVE OCCURRENCE, naming Shawn P.Firminger, Jason Garms, Edward K. Y. Jung, Chris D. Karkanias, Eric C.Leuthardt, Royce A. Levien, Robert W. Lord, Mark A. Malamud, John D.Rinaldo, Jr., Clarence T. Tegreene, Kristin M. Tolle, and Lowell L.Wood, Jr., as inventors, filed 30 Apr. 2009, which is currentlyco-pending, or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/387,465, entitled HYPOTHESIS BASED SOLICITATIONOF DATA INDICATING AT LEAST ONE OBJECTIVE OCCURRENCE, naming Shawn P.Firminger, Jason Garms, Edward K. Y. Jung, Chris D. Karkanias, Eric C.Leuthardt, Royce A. Levien, Robert W. Lord, Mark A. Malamud, John D.Rinaldo, Jr., Clarence T. Tegreene, Kristin M. Tolle, and Lowell L.Wood, Jr., as inventors, filed 30 Apr. 2009, which is currentlyco-pending, or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/455,309, entitled HYPOTHESIS DEVELOPMENT BASEDON SELECTIVE REPORTED EVENTS, naming Shawn P. Firminger, Jason Garms,Edward K. Y. Jung, Chris D. Karkanias, Eric C. Leuthardt, Royce A.Levien, Robert W. Lord, Mark A. Malamud, John D. Rinaldo, Jr., ClarenceT. Tegreene, Kristin M. Tolle, and Lowell L. Wood, Jr., as inventors,filed 28 May 2009, which is currently co-pending, or is an applicationof which a currently co-pending application is entitled to the benefitof the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/455,317, entitled HYPOTHESIS DEVELOPMENT BASEDON SELECTIVE REPORTED EVENTS, naming Shawn P. Firminger, Jason Garms,Edward K. Y. Jung, Chris D. Karkanias, Eric C. Leuthardt, Royce A.Levien, Robert W. Lord, Mark A. Malamud, John D. Rinaldo, Jr., ClarenceT. Tegreene, Kristin M. Tolle, and Lowell L. Wood, Jr., as inventors,filed 29 May 2009, which is currently co-pending, or is an applicationof which a currently co-pending application is entitled to the benefitof the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/456,249, entitled HYPOTHESIS SELECTION ANDPRESENTATION OF ONE OR MORE ADVISORIES, naming Shawn P. Firminger, JasonGarms, Edward K. Y. Jung, Chris D. Karkanias, Eric C. Leuthardt, RoyceA. Levien, Robert W. Lord, Mark A. Malamud, John D. Rinaldo, Jr.,Clarence T. Tegreene, Kristin M. Tolle, and Lowell L. Wood, Jr., asinventors, filed 12 Jun. 2009, which is currently co-pending, or is anapplication of which a currently co-pending application is entitled tothe benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/456,433, entitled HYPOTHESIS SELECTION ANDPRESENTATION OF ONE OR MORE ADVISORIES, naming Shawn P. Firminger, JasonGarms, Edward K. Y. Jung, Chris D. Karkanias, Eric C. Leuthardt, RoyceA. Levien, Robert W. Lord, Mark A. Malamud, John D. Rinaldo, Jr.,Clarence T. Tegreene, Kristin M. Tolle, and Lowell L. Wood, Jr., asinventors, filed 15 Jun. 2009, which is currently co-pending, or is anapplication of which a currently co-pending application is entitled tothe benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/459,775, entitled HYPOTHESIS DEVELOPMENT BASEDON USER AND SENSING DEVICE DATA, naming Shawn P. Firminger, Jason Garms,Edward K. Y. Jung, Chris D. Karkanias, Eric C. Leuthardt, Royce A.Levien, Robert W. Lord, Mark A. Malamud, John D. Rinaldo, Jr., ClarenceT. Tegreene, Kristin M. Tolle, and Lowell L. Wood, Jr., as inventors,filed 6 Jul. 2009, which is currently co-pending, or is an applicationof which a currently co-pending application is entitled to the benefitof the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/459,854, entitled HYPOTHESIS DEVELOPMENT BASEDON USER AND SENSING DEVICE DATA, naming Shawn P. Firminger, Jason Garms,Edward K. Y. Jung, Chris D. Karkanias, Eric C. Leuthardt, Royce A.Levien, Robert W. Lord, Mark A. Malamud, John D. Rinaldo, Jr., ClarenceT. Tegreene, Kristin M. Tolle, and Lowell L. Wood, Jr., as inventors,filed 7 Jul. 2009, which is currently co-pending, or is an applicationof which a currently co-pending application is entitled to the benefitof the filing date.

The United States Patent Office (USPTO) has published a notice to theeffect that the USPTO's computer programs require that patent applicantsreference both a serial number and indicate whether an application is acontinuation or continuation-in-part. Stephen G. Kunin, Benefit ofPrior-Filed Application, USPTO Official Gazette Mar. 18, 2003, availableat http://www.uspto.gov/web/offices/com/sol/og/2003/week11/patbene.htm.The present Applicant Entity (hereinafter “Applicant”) has providedabove a specific reference to the application(s) from which priority isbeing claimed as recited by statute. Applicant understands that thestatute is unambiguous in its specific reference language and does notrequire either a serial number or any characterization, such as“continuation” or “continuation-in-part,” for claiming priority to U.S.patent applications. Notwithstanding the foregoing, Applicantunderstands that the USPTO's computer programs have certain data entryrequirements, and hence Applicant is designating the present applicationas a continuation-in-part of its parent applications as set forth above,but expressly points out that such designations are not to be construedin any way as any type of commentary and/or admission as to whether ornot the present application contains any new matter in addition to thematter of its parent application(s).

All subject matter of the Related Applications and of any and allparent, grandparent, great-grandparent, etc. applications of the RelatedApplications is incorporated herein by reference to the extent suchsubject matter is not inconsistent herewith.

SUMMARY

A computationally implemented method includes, but is not limited topresenting to a user a hypothesis identifying at least a relationshipbetween a first event type and a second event type; receiving from theuser one or more modifications to modify the hypothesis; and executingone or more actions based, at least in part, on a modified hypothesisresulting, at least in part, from the reception of the one or moremodifications. In addition to the foregoing, other method aspects aredescribed in the claims, drawings, and text forming a part of thepresent disclosure.

In one or more various aspects, related systems include but are notlimited to circuitry and/or programming for effecting theherein-referenced method aspects; the circuitry and/or programming canbe virtually any combination of hardware, software, and/or firmwareconfigured to effect the herein-referenced method aspects depending uponthe design choices of the system designer.

A computationally implemented system includes, but is not limited to:means for presenting to a user a hypothesis identifying at least arelationship between a first event type and a second event type; meansfor receiving from the user one or more modifications to modify thehypothesis; and means for executing one or more actions based, at leastin part, on a modified hypothesis resulting, at least in part, from thereception of the one or more modifications. In addition to theforegoing, other system aspects are described in the claims, drawings,and text forming a part of the present disclosure.

A computationally implemented system includes, but is not limited to:circuitry for presenting to a user a hypothesis identifying at least arelationship between a first event type and a second event type;circuitry for receiving from the user one or more modifications tomodify the hypothesis; and circuitry for executing one or more actionsbased, at least in part, on a modified hypothesis resulting, at least inpart, from the reception of the one or more modifications. In additionto the foregoing, other system aspects are described in the claims,drawings, and text forming a part of the present disclosure.

A computer program product including a signal-bearing medium bearing oneor more instructions presenting to a user a hypothesis identifying atleast a relationship between a first event type and a second event type;one or more instructions for receiving from the user one or moremodifications to modify the hypothesis; and one or more instructions forexecuting one or more actions based, at least in part, on a modifiedhypothesis resulting, at least in part, from the reception of the one ormore modifications. In addition to the foregoing, other computer programproduct aspects are described in the claims, drawings, and text forminga part of the present disclosure.

The foregoing summary is illustrative only and is not intended to be inany way limiting. In addition to the illustrative aspects, embodiments,and features described above, further aspects, embodiments, and featureswill become apparent by reference to the drawings and the followingdetailed description.

BRIEF DESCRIPTION OF THE FIGURES

FIGS. 1 a and 1 b show a high-level block diagram a computing device 10and a mobile device 30 operating in a network environment.

FIG. 2 a shows another perspective of the hypothesis presentation module102 of the computing device 10 of FIG. 1 b.

FIG. 2 b shows another perspective of the modification reception module104 of the computing device 10 of FIG. 1 b.

FIG. 2 c shows another perspective of the action execution module 108 ofthe computing device 10 of FIG. 1 b.

FIG. 2 d shows another perspective of the mobile device 30 of FIG. 1 a.

FIG. 2 e shows another perspective of the hypothesis presentation module102′ of the mobile device 30 of FIG. 2 d.

FIG. 2 f shows another perspective of the modification reception module104′ of the mobile device 30 of FIG. 2 d.

FIG. 2 g shows another perspective of the action execution module 108′of the mobile device 30 of FIG. 2 d.

FIG. 2 h shows an exemplarily user interface display displaying a visualversion of a hypothesis.

FIG. 2 i shows another exemplarily user interface display displayinganother visual version of the hypothesis.

FIG. 2 j shows another exemplarily user interface display displayingstill another visual version of the hypothesis.

FIG. 2 k shows another exemplarily user interface display displaying avisual version of another hypothesis.

FIG. 3 is a high-level logic flowchart of a process.

FIG. 4 a is a high-level logic flowchart of a process depictingalternate implementations of the hypothesis presentation operation 302of FIG. 3.

FIG. 4 b is a high-level logic flowchart of a process depictingalternate implementations of the hypothesis presentation operation 302of FIG. 3.

FIG. 4 c is a high-level logic flowchart of a process depictingalternate implementations of the hypothesis presentation operation 302of FIG. 3.

FIG. 4 d is a high-level logic flowchart of a process depictingalternate implementations of the hypothesis presentation operation 302of FIG. 3.

FIG. 4 e is a high-level logic flowchart of a process depictingalternate implementations of the hypothesis presentation operation 302of FIG. 3.

FIG. 4 f is a high-level logic flowchart of a process depictingalternate implementations of the hypothesis presentation operation 302of FIG. 3.

FIG. 5 a is a high-level logic flowchart of a process depictingalternate implementations of the modification reception operation 304 ofFIG. 3.

FIG. 5 b is a high-level logic flowchart of a process depictingalternate implementations of the modification reception operation 304 ofFIG. 3.

FIG. 6 a is a high-level logic flowchart of a process depictingalternate implementations of the action execution operation 306 of FIG.3.

FIG. 6 b is a high-level logic flowchart of a process depictingalternate implementations of the action execution operation 306 of FIG.3.

FIG. 6 c is a high-level logic flowchart of a process depictingalternate implementations of the action execution operation 306 of FIG.3.

FIG. 6 d is a high-level logic flowchart of a process depictingalternate implementations of the action execution operation 306 of FIG.3.

FIG. 6 e is a high-level logic flowchart of a process depictingalternate implementations of the action execution operation 306 of FIG.3.

DETAILED DESCRIPTION

In the following detailed description, reference is made to theaccompanying drawings, which form a part hereof. In the drawings,similar symbols typically identify similar components, unless contextdictates otherwise. The illustrative embodiments described in thedetailed description, drawings, and claims are not meant to be limiting.Other embodiments may be utilized, and other changes may be made,without departing from the spirit or scope of the subject matterpresented here.

A recent trend that is becoming increasingly popular in thecomputing/communication field is to electronically record one'sfeelings, thoughts, and other aspects of the person's everyday life ontoan open diary. One place where such open diaries are maintained are atsocial networking sites commonly known as “blogs” where users may reportor post their latest status, personal activities, and various otheraspects of the users' everyday life. The process of reporting or postingblog entries is commonly referred to as blogging. Other socialnetworking sites may allow users to update their personal informationvia, for example, social networking status reports in which a user mayreport or post for others to view their current status, activities,and/or other aspects of the user.

A more recent development in social networking is the introduction andexplosive growth of microblogs in which individuals or users (referredto as “microbloggers”) maintain open diaries at microblog websites(e.g., otherwise known as “twitters”) by continuously orsemi-continuously posting microblog entries. A microblog entry (e.g.,“tweet”) is typically a short text message that is usually not more than140 characters long. The microblog entries posted by a microblogger mayreport on any aspect of the microblogger's daily life. Typically, suchmicroblog entries will describe the various “events” associated with orare of interest to the microblogger that occurs during a course of atypical day. The microblog entries are often continuously posted duringthe course of a typical day, and thus, by the end of a normal day, asubstantial number of events may have been reported and posted.

Each of the reported events that may be posted through microblog entriesmay be categorized into one of at least three possible categories. Thefirst category of events that may be reported through microblog entriesare “objective occurrences” that may or may not be associated with themicroblogger. Objective occurrences that are associated with amicroblogger may be any characteristic, incident, happening, or anyother event that occurs with respect to the microblogger or are ofinterest to the microblogger that can be objectively reported by themicroblogger, a third party, or by a device. Such events would include,for example, intake of food, medicine, or nutraceutical, certainphysical characteristics of the microblogger such as blood sugar levelor blood pressure, activities of the microblogger, external events suchas performance of the stock market (which the microblogger may have aninterest in), performance of a favorite sports team, and so forth.

Other examples of objective occurrences include, for example, externalevents such as the local weather, activities of others (e.g., spouse orboss), the behavior or activities of a pet or livestock, thecharacteristics or performances of mechanical or electronic devices suchas automobiles, appliances, and computing devices, and other events thatmay directly or indirectly affect the microblogger.

A second category of events that may be reported or posted throughmicroblog entries include “subjective user states” of the microblogger.Subjective user states of a microblogger may include any subjectivestate or status associated with the microblogger that can only betypically reported by the microblogger (e.g., generally cannot bedirectly reported by a third party or by a device). Such statesincluding, for example, the subjective mental state of the microblogger(e.g., happiness, sadness, anger, tension, state of alertness, state ofmental fatigue, jealousy, envy, and so forth), the subjective physicalstate of the microblogger (e.g., upset stomach, state of vision, stateof hearing, pain, and so forth), and the subjective overall state of themicroblogger (e.g., “good,” “bad,” state of overall wellness, overallfatigue, and so forth). Note that the term “subjective overall state” aswill be used herein refers to those subjective states that may not fitneatly into the other two categories of subjective user states describedabove (e.g., subjective mental states and subjective physical states).

A third category of events that may be reported or posted throughmicroblog entries include “subjective observations” made by themicroblogger. A subjective observation is similar to subjective userstates and may be any subjective opinion, thought, or evaluationrelating to any external incidence (e.g., outward looking instead ofinward looking as in the case of subjective user states). Thus, thedifference between subjective user states and subjective observations isthat subjective user states relates to self-described subjectivedescriptions of the user states of one's self while subjectiveobservations relates to subjective descriptions or opinions regardingexternal events. Examples of subjective observations include, forexample, a microblogger's perception about the subjective user state ofanother person (e.g., “he seems tired”), a microblogger's perceptionabout another person's activities (e.g., “he drank too much yesterday”),a microblogger's perception about an external event (e.g., “it was anice day today”), and so forth. Although microblogs are being used toprovide a wealth of personal information, thus far they have beenprimarily limited to their use as a means for providing commentaries andfor maintaining open diaries.

Another potential source for valuable but yet to be fully exploited isdata that may be provided by sensing devices that are used to senseand/or monitor various aspects of everyday life. Currently there are anumber of sensing devices that can detect and/or monitor varioususer-related and nonuser-related events. For example, there arepresently a number of sensing devices that can sense various physical orphysiological characteristics of a person or an animal (e.g., a pet or alivestock). Examples of such devices include commonly known and usedmonitoring devices such as blood pressure devices, heart rate monitors,blood glucose sensors (e.g., glucometers), respiration sensor devices,temperature sensors, and so forth. Other examples of devices that canmonitor physical or physiological characteristics include more exoticand sophisticated devices such as functional magnetic resonance imaging(fMRI) device, functional Near Infrared (fNIR) devices, bloodcell-sorting sensing device, and so forth. Many of these devices arebecoming more compact and less expensive such that they are becomingincreasingly accessible for purchase and/or self-use by the generalpublic.

Other sensing devices may be used in order to sense and for monitoractivities of a person or an animal. These would include, for example,global positioning systems (GPS), pedometers, accelerometers, and soforth. Such devices are compact and can even be incorporated into, forexample, a mobile communication device such a cellular telephone or onthe collar of a pet. Other sensing devices for monitoring activities ofindividuals (e.g., users) may be incorporated into larger machines andmay be used in order to monitor the usage of the machines by theindividuals. These would include, for example, sensors that areincorporated into exercise machines, automobiles, bicycles, and soforth. Today there are even toilet monitoring devices that are availableto monitor the toilet usage of individuals.

Other sensing devices are also available that can monitor generalenvironmental conditions such as environmental temperature sensordevices, humidity sensor devices, barometers, wind speed monitors, watermonitoring sensors, air pollution sensor devices (e.g., devices that canmeasure the amount of particulates in the air such as pollen, those thatmeasure CO₂ levels, those that measure ozone levels, and so forth).Other sensing devices may be employed in order to monitor theperformance or characteristics of mechanical and/or electronic devices.All the above described sensing devices may provide useful data that mayindicate objectively observable events (e.g., objective occurrences).

In accordance with various embodiments, the data provided through socialnetworking sites (e.g., via microblog entries, status entries, diaryentries, and so forth) as well as, in some cases, those from sensingdevices may be processed in order to develop a hypotheses thatidentifies the relationship between multiple event types (e.g., types ofevents). For example, based on past events reported by a person (e.g., amicroblogger) and/or reported by sensing devices, a hypothesis such as ahypothesis may be developed relating to the person, a third party, adevice, external activities, environmental conditions, or anything elsethat may be of interest to the person. One way to develop or create sucha hypothesis is by identifying a pattern of events that repeatedlyreoccurs.

Once such a hypothesis is developed, one or more actions may be executedbased on the hypothesis and in response to, for example, occurrence ofone or more reported events that may match or substantially match one ormore of the event types identified in the hypothesis. Examples ofactions that could be executed include, for example, the presentation ofadvisories or the prompting of one or more devices (e.g., sensingdevices or home appliances) to execute one or more operations. However,the development of a hypothesis based on identifying repeatedlyreoccurring patterns of events may lead to the development of a faultyor incorrect hypothesis.

As an illustration, suppose a hypothesis is developed by identifying arepetitively reoccurring pattern of events that indicate, for example,that whenever the person wakes-up late, eats ice cream, and drinkscoffee, a stomach ache follows. However, merely looking at repetitivelyreoccurring patterns of events may result in a hypothesis that includestypes of events that may not be relevant to the hypothesis or may notaccurately reflect the types of events that should be included in thehypothesis. For example, in the above example, waking-up late may not berelevant to having a stomach ache. That is, the hypothesis may have beenbased on data that indicated that prior to past occurrences ofstomachaches, the subject (e.g., user) had reported waking-up late,eating ice cream, and drinking coffee. However, the reports of waking-uplate occurring prior to previous reports of stomachaches may merely havebeen a coincidence. As can be seen, using the technique determiningrepeatedly reoccurring patterns of events may result in the developmentof inaccurate or even false hypothesis.

Accordingly, robust methods, systems, and computer program products areprovided to, among other things, present to a user a hypothesisidentifying at least a relationship between a first event type and asecond event type and receive from the user one or more modifications tomodify the hypothesis. The methods, systems, and computer programproducts may then facilitate in the execution of one or more actionsbased, at least in part, on a modified hypothesis resulting, at least inpart, from the reception of the one or more modifications. Examples ofthe types of actions that may be executed include, for example, thepresentation of the modified hypothesis or advisories relating to themodified hypothesis. Other actions that may be executed include theprompting of mechanical and/or electronic devices to execute one or moreoperations based, at least in part, on the modified hypothesis. In somecases, the execution of the one or more actions, in addition to beingbased on the modified hypothesis, may be in response to a reportedevent.

The robust methods, systems, and computer program products may beemployed in a variety of environments including, for example, socialnetworking environments, blogging or microblogging environments, instantmessaging (IM) environments, or any other type of environment thatallows a user to, for example, maintain a diary. Further, the methods,systems, and computing program products in various embodiments may beimplemented in a standalone computing device or implemented in aclient/server environment.

In various implementations, a “hypothesis,” as referred to herein, maydefine one or more relationships or links between different types ofevents (i.e., event types) including defining a relationship between atleast a first event type (e.g., a type of event such as a particulartype of subjective user state including, for example, a subjectivemental state such as “happy”) and a second event type (e.g., anothertype of event such as a particular type of objective occurrence, forexample, favorite sports team winning a game). In some cases, ahypothesis may be represented by an events pattern that may indicatespatial or sequential (e.g., time/temporal) relationships betweendifferent event types (e.g., subjective user states, subjectiveobservations, and/or objective occurrences). In some embodiments, ahypothesis may be further defined by an indication of the soundness(e.g., strength) of the hypothesis.

Note that for ease of explanation and illustration, the followingdescription will describe a hypothesis as defining, for example, thesequential or spatial relationships between two, three, or four eventtypes. However, those skilled in the art will recognize that such ahypothesis may also identify the relationships between five or moreevent types (e.g., a first event type, a second event type, a thirdevent type, a fourth event type, a fifth event type, and so forth).

In some embodiments, a hypothesis may, at least in part, be defined orrepresented by an events pattern that indicates or suggests a spatial ora sequential (e.g., time/temporal) relationship between different eventtypes. Such a hypothesis, in some cases, may also indicate the strengthor weakness of the link between the different event types. That is, thestrength or weakness (e.g., soundness) of the correlation betweendifferent event types may depend upon, for example, whether the eventspattern repeatedly occurs and/or whether a contrasting events patternhas occurred that may contradict the hypothesis and therefore, weakenthe hypothesis (e.g., an events pattern that indicates a person becomingtired after jogging for thirty minutes when a hypothesis suggests that aperson will be energized after jogging for thirty minutes).

As briefly described above, a hypothesis may be represented by an eventspattern that may indicate spatial or sequential (e.g., time or temporal)relationship or relationships between multiple event types. In someimplementations, a hypothesis may indicate a temporal relationship orrelationships between multiple event types. In alternativeimplementations a hypothesis may indicate a more specific timerelationship or relationships between multiple event types. For example,a sequential pattern may represent the specific pattern of events thatoccurs along a timeline that may specify the specific amount of time, ifthere are any, between occurrences of the event types. In still otherimplementations, a hypothesis may indicate the specific spatial (e.g.,geographical) relationship or relationships between multiple eventtypes.

In various embodiments, a hypothesis may initially be provided to a user(e.g., a microblogger or a social networking user) that the hypothesismay or may not be directly associated with. That is, in someembodiments, a hypothesis may be initially provided that directlyrelates to a user. Such a hypothesis may relate to, for example, one ormore subjective user states associated with the user, one or moreactivities associated with the user, or one or more characteristicsassociated with the user. In other embodiments, however, a hypothesismay be initially provided that may not be directly associated with auser. For example, a hypothesis may be initially provided that may beparticularly associated with a third party (e.g., a spouse of the user,a friend, a pet, and so forth), while in other embodiments, a hypothesismay be initially provided that is directed to a device that may be, forexample, operated or used by the user. In still other cases, ahypothesis may be provided that relates to one or more environmentalcharacteristics or conditions.

In some embodiments, the hypothesis to be initially provided to a usermay have been originally created based, for example, on reported eventsas reported by the user through, for example, blog entries, statusreports, diary entries, and so forth. Alternatively, such a hypothesismay be supplied by a third party source such as a network serviceprovider or a content provider.

After being presented with the hypothesis, the user may be provided withan opportunity to modify the presented hypothesis. Various types ofmodifications may be made by the user including, for example, revisingor deleting one or more event types identified by the hypothesis,revising one or more relationships between the multiple event typesidentified by the hypothesis, or adding new event types to thehypothesis. Based on the modifications provided by the user, a modifiedhypothesis may be generated. In some embodiments, the user may beprovided with the option to delete or deactivate the hypothesis or anoption to select or revise the type of actions that may be executedbased on the modified hypothesis.

Based, at least in part, on the modified hypothesis, one or more actionsmay be executed. Examples of the types of actions that may be executedinclude, for example, presenting to the user or a third party one ormore advisories related to the modified hypothesis or prompting one ormore devices to execute one or more operations based on the modifiedhypothesis. The one or more advisories that may be presented mayinclude, for example, presentation of the modified hypothesis,presentation of a recommendation for a future action, presentation of aprediction of a future event, and/or presentation of a past event orevents. Examples of the types of devices that may be prompted to executeone or more operations include, for example, sensing devices (e.g.,sensing devices that can sense physiological or physical characteristicsof the user or a third party, sensing devices that can sense theactivities of the user or a third party, sensing devices to monitorenvironmental conditions, and so forth), household appliances, computingor communication devices, environmental devices (e.g., air conditioner,humidifier, air purifier, and so forth), and/or other types ofelectronic/mechanical devices. In some embodiments, the one or moreactions may be in response to, in addition to being based on themodified hypothesis, a reported event.

FIGS. 1 a and 1 b illustrate an example environment in accordance withvarious embodiments. In the illustrated environment, an exemplary system100 may include at least a computing device 10 (see FIG. 1 b). In someembodiments, the computing device 10 may be a server (e.g., networkserver), which may communicate with a user 20 a via a mobile device 30and through a wireless and/or wired network 40. In other embodiments,the computing device 10 may be a standalone device, which maycommunicate directly with a user 20 b via a user interface 122.

Regardless of whether the computing device 10 is a network server or astandalone device, the computing device 10 may be designed to, amongother things, present to a user 20* a hypothesis 60 that identifies atleast a relationship between a first event type and a second event type,receive from the user 20* one or more modifications 61 to modify thehypothesis 60, and execute one or more actions based, at least in part,on a modified hypothesis 80 resulting, at least in part, from thereception of the one or more modifications 61. As will be furtherdescribed herein, in embodiments where the computing device 10 is aserver that communicates with a user 20 a via the mobile device 30, themobile device 30 may also be designed to perform the above-describedoperations. In the following, “*” indicates a wildcard. Thus, referencesto user 20* may indicate a user 20 a or a user 20 b of FIGS. 1 a and 1b. Similarly, references to sensing devices 35* may be a reference tosensing devices 35 a or sensing devices 35 b of FIGS. 1 a and 1 b.

As indicated earlier, in some embodiments, the computing device 10 maybe a network server (or simply “server”) while in other embodiments thecomputing device 10 may be a standalone device. In the case where thecomputing device 10 is a network server, the computing device 10 maycommunicate indirectly with a user 20 a, one or more third parties 50,and one or more sensing devices 35 a via wireless and/or wired network40. A network server, as will be described herein, may be in referenceto a server located at a single network site or located across multiplenetwork sites or a conglomeration of servers located at multiple networksites. The wireless and/or wired network 40 may comprise of, forexample, a local area network (LAN), a wireless local area network(WLAN), personal area network (PAN), Worldwide Interoperability forMicrowave Access (WiMAX), public switched telephone network (PTSN),general packet radio service (GPRS), cellular networks, and/or othertypes of wireless or wired networks. In contrast, in embodiments wherethe computing device 10 is a standalone device, the computing device 10may at least directly communicate with a user 20 b (e.g., via a userinterface 122) and one or more sensing devices 35 b.

The mobile device 30 may be a variety of computing/communication devicesincluding, for example, a cellular phone, a personal digital assistant(PDA), a laptop, a desktop, or other types of computing/communicationdevices that can communicate with the computing device 10. In someembodiments, the mobile device 30 may be a handheld device such as acellular telephone, a smartphone, a Mobile Internet Device (MID), anUltra Mobile Personal Computer (UMPC), a convergent device such as apersonal digital assistant (PDA), and so forth.

In embodiments in which the computing device 10 is a standalone device,the computing device 10 may be any type of portable device (e.g., ahandheld device) or non-portable device (e.g., desktop computer orworkstation). For these embodiments, the computing device 10 may be anyone of a variety of computing/communication devices including, forexample, a cellular phone, a personal digital assistant (PDA), a laptop,a desktop, or other types of computing/communication devices. In someembodiments, in which the computing device 10 is a handheld device, thecomputing device 10 may be a cellular telephone, a smartphone, an MID,an UMPC, a convergent device such as a PDA, and so forth. In variousembodiments, the computing device 10 may be a peer-to-peer networkcomponent device. In some embodiments, the computing device 10 and/orthe mobile device 30 may operate via a Web 2.0 construct (e.g., Web 2.0application 268).

The one or more sensing devices 35* may include one or more of a varietyof different types of sensing/monitoring devices to sense variousaspects (e.g., characteristics, features, or activities) associated witha user 20*, one or more third parties 50, one or more network and/orlocal devices 55, one or more external activities, one or moreenvironmental characteristics, and so forth. Examples of such sensingdevices 35* include, for example, those devices that can measurephysical or physical characteristics of a subject (e.g., a user 20* or athird party 50) such as a heart rate sensor device, blood pressuresensor device, blood glucose sensor device, functional magneticresonance imaging (fMRI) device, a functional near-infrared (fNIR)device, blood alcohol sensor device, temperature sensor device (e.g.,thermometer), respiration sensor device, blood cell-sorting sensordevice (e.g., to sort between different types of blood cells), and soforth. Another type of devices that may be included in the one or moresensing devices 35 includes, for example, those that can sense theactivities of their subjects (e.g., user 20* or a third party 50).Examples of such devices include, for example, pedometers,accelerometers, an image capturing device (e.g., digital or videocamera), toilet monitoring devices, exercise machine sensor devices, andso forth. Other types of sensing devices 35* include, for example,global positioning system (GPS) devices, environmental sensors such as aroom thermometer, barometer, air quality sensor device, humidity sensordevice, sensing devices to sense characteristics or operationalperformances of devices, and so forth.

The one or more third parties 50 depicted in FIG. 1 a may include, forexample, one or more persons (e.g., a spouse, a friend, a socialnetworking group, a co-worker, and so forth), one or more animals (e.g.,a pet or livestock), and/or business entities (e.g., content provider,network service provider, etc.).

There are at least two ways that the computing device 10 may initiallyacquire a hypothesis 60. One way is to acquire the hypothesis 60 from athird party source such as a network service provider, a contentprovider, or an application provider. A second way is to self-developthe hypothesis 60. For example, in various implementations, andregardless of whether the computing device 10 is a standalone device oras a network server, a hypothesis 60 may be initially developed (e.g.,created) by the computing device 10 based, at least in part, on eventsdata that may be provided by one or more sources (e.g., a user 20*, oneor more third parties 50, or one or more sensing devices 35*). Theevents data provided by the one or more sources may indicate past eventsas reported by the sources. In some cases, such data may be provided bythe one or more sources via electronic entries such as blog entries(e.g., microblog entries), status reports, electronic messages (email,instant messages (IMs), etc.), diary entries, and so forth.

By identifying a repeatedly reoccurring pattern of reported events, forexample, a hypothesis 60 may be developed by the computing device 10.The resulting hypothesis 60 may indicate a spatial or a sequential(temporal or specific time) relationship between at least a first eventtype (e.g., a type of subjective user state, a type of subjectiveobservation, or a type of objective occurrence) and a second event type(e.g., a type of subjective user state, a type of subjectiveobservation, or a type of objective occurrence).

The computing device 10 may then present (e.g., indicate via a userinterface 122 or transmit via the wireless and/or wired network 40) to auser 20* the hypothesis 60. In embodiments where the computing device 10is a server, the computing device 10 may present the hypothesis 60 to auser 20 a by transmitting the hypothesis 60 to the mobile device 30 viathe wireless and/or wired network 40. The mobile device 30 may thenaudioally and/or visually present the hypothesis 60 to the user 20 a. Onthe other hand, in embodiments where the computing device 10 is astandalone device, the hypothesis 60 may be directly presented to a user20 b by audioally or visually indicating the hypothesis 60 to the user20 a via a user interface 122.

The hypothesis 60 may be presented to a user 20*(e.g., user 20 a or user20 b) in a variety of different ways. For example, in variousimplementations, the hypothesis 60* may be presented in graphical form,in pictorial form, in textual form, in audio form and so forth. In someimplementations, the hypothesis 60 to be presented may be modifiablesuch that one or more event types and/or their relationships (e.g.,spatial or temporal/time relationships) with respect to each other thatare identified by the hypothesis 60 may be revised or even deleted. Suchmodifiable hypothesis 60 may also allow a user 20* to add to thehypothesis 60 additional event types with respect to the event typesalready included in the hypothesis 60. In some implementations, thecomputing device 10 may present to the user 20* an option to delete ordeactivate the hypothesis 60.

After presenting the hypothesis 60 to the user 20*, the computing device10 may be designed to receive from the user 20* one or moremodifications 61 to modify the hypothesis 60. In embodiments in whichthe computing device 10 is a server, the computing device 10 may receivethe one or more modifications 61 from the user 20 a through mobiledevice 30 and via the wireless and/or wired network 40. Note that forthese embodiments, the mobile device 30 may directly receive the one ormore modifications 61 from the user 20 a and may then transmit the oneor more modifications 61 to the computing device 10. In alternativeembodiments in which the computing device 10 is a standalone device, thecomputing device 10 may receive the one or more modifications 61directly from the user 20 b via a user interface 122.

In various implementations, the one or more modifications 61 receivedfrom the user 20* may be for revising and/or deleting one or more eventtypes and their relationships with respect to each other that areindicated by the hypothesis 60. In some cases, the one or moremodifications 61 may also include modifications to add one or more eventtypes with to respect to the event types already included in thehypothesis 60. In other words, the one or more modifications 61 to bereceived by the computing device 10 and/or by the mobile device 30 mayinclude one or more modifications for adding one or more event types tothe hypothesis 60 and their relationships (e.g., spatial or temporalrelationships) with the event types already included in the hypothesis60. Note that in some cases, the computing device 10 (as well as themobile device 30) may receive from the user 20*, an indication of one ormore actions to be executed based, at least in part, on the resultingmodified hypothesis 80.

In any event, the computing device 10 may then generate a modifiedhypothesis 80 by modifying the hypothesis 60 based on the one or moremodifications 61 received from the user 20*(user 20 a or user 20 b). Insome embodiments, the modified hypothesis 80 may be stored in memory140.

The computing device 10 (as well as the mobile device 30) may thenexecute one or more actions based, at least in part, on the modifiedhypothesis 80 resulting from the reception of the one or moremodifications 61 by the computing device 10. Various types of actionsmay be executed by the computing device 10 and/or by the mobile device30 in various alternative embodiments. For example, in some embodiments,the computing device 10 and/or the mobile device 30 may present one ormore advisories 90 to a user 20* or to one or more third parties 50. Forinstance, in embodiments where the computing device 10 is a server, thecomputing device 10 may present the one or more advisories 90 to a user20 a by transmitting the one or more advisories 90 to the mobile device30 (or to one or more third parties 50) via a wireless and/or wirednetwork 40. The mobile device 30 may then present the one or moreadvisories 90 to a user 20 a by audioally and/or visually indicating tothe user 20 a (e.g., via an audio and/or display system) the one or moreadvisories 90.

In embodiments in which the computing device 10 is a standalone device,the computing device 10 may present the one or more advisories 90 to auser 20 b by audioally and/or visually indicating to the user 20 b(e.g., via an audio and/or display system) the one or more advisories.For these embodiments, the computing device 10 may present the one ormore advisories 90 to one or more third parties 50 by transmitting theone or more advisories 90 to the one or more third parties 50 via awireless and/or wired network 40.

The one or more advisories 90 to be presented by the computing device 10or by the mobile device 30 may be one or more of a variety of advisoriesthat may be associated with the modified hypothesis 80 and that can bepresented. For example, in some implementations, the one or moreadvisories 90 to be presented may include at least one form (e.g., anaudio form, a graphical form, a pictorial form, a textual form, and soforth) of the modified hypothesis 80. In the same or differentimplementations, the one or more advisories 90 to be presented mayinclude a prediction of a future event or an indication of an occurrenceof a past reported event. In the same or different implementations, theone or more advisories 90 to be presented may include a recommendationfor a future course of action and in some cases, justification for therecommendation.

In some embodiments, the computing device 10 and/or the mobile device 30may execute one or more actions by prompting 91* one or more devices(e.g., one or more sensing devices 35* and/or one or more network/localdevices 55) to execute one or more operations. For example, prompting91* one or more sensing devices 35* to sense various characteristicsassociated with a user 20* or a third party 50, or prompting one or morehousehold devices (which may be network and/or local devices 55) toperform one or more operations. Note that references to “prompting oneor more to execute one or more devices” herein may be in reference todirecting, instructing, activating, requesting, and so forth, one ormore devices to execute one or more operations.

In embodiments in which the computing device 10 is a server, thecomputing device 10 may indirectly or directly prompt one or moredevices. For example, in some embodiments, the computing device 10 mayindirectly prompt one or more devices to execute one or more operationsby transmitting to the mobile device 30 a request or instructions toprompt other devices to execute one or more operations. In response tothe request or instructions transmitted by the computing device 10, themobile device 30 may directly prompt 91′ one or more devices (e.g.,sensing devices 35* and/or network and/or local devices 55) to executeone or more operations. In the same or different embodiments, thecomputing device 10 may alternatively or complimentarily directly prompt91 the one or more devices (e.g., sensing devices 35 and/or networkand/or local devices 55) to execute one or more operations. Inembodiments in which the computing device 10 is a standalone device, thecomputing device 10 may directly (e.g., without going through mobiledevice 30) prompt 91 the one or more devices (e.g., sensing devices 35*and/or network and/or local devices 55) to execute the one or moreoperations.

In some embodiments, the one or more actions to be executed by thecomputing device 10 or by the mobile device 30 may be in response, atleast in part, to a reported event. For instance, the one or moreactions to be executed by the computing device 10 or by the mobiledevice 30 may be in response to a reported event 62 that at leastsubstantially matches with at least one of the event types identified bythe modified hypothesis 80. To illustrate, suppose the modifiedhypothesis 80 indicates that the gas tank of car belonging to a user 20*is always empty (e.g., a first event type) whenever a particular friendreturns a car after borrowing it (e.g., a second event type). Inresponse to receiving data (e.g., in the form of a blog entry or statusreport) that indicates that the particular friend has again borrowed andreturned the user's car (e.g., reported event 62), and based at least inpart on the modified hypothesis 80, the computing device 10 may executeone or more actions (e.g., transmitting one or more advisories such as awarning to fill-up the gas tank to the mobile device 30). In thisexample, the computing device 10 may execute the one or more actionsbecause the reported event 62 at least substantially matches the secondevent type as identified by the modified hypothesis 80. Note that thereported event 62 that may initiate the one or more actions to beexecuted by the computing device 10 or the mobile device 30 (which inthe above example, may execute one or more actions by audioally orvisually indicating the one or more advisories 90) may be reported by auser 20*, one or more third parties 50, or from one or more sensingdevices 35*.

Referring particularly now to the computing device 10 of FIG. 1 b, whichmay include one or more components and/or modules. As those skilled inthe art will recognize, these components and modules may be implementedby employing hardware (e.g., in the form of circuitry such asapplication specific integrated circuit or ASIC, field programmable gatearray or FPGA, or other types of circuitry), software, a combination ofboth hardware and software, or may be implemented by a general purposecomputing device executing instructions included in a signal-bearingmedium.

In various embodiments, the computing device 10 may include a hypothesispresentation module 102, a modification reception module 104, ahypothesis modification module 106, an action execution module 108, areported event reception module 110, a hypothesis development module112, a network interface 120 (e.g., network interface card or NIC), auser interface 122 (e.g., a display monitor, a touchscreen, a keypad orkeyboard, a mouse, an audio system including a microphone and/orspeakers, an image capturing system including digital and/or videocamera, and/or other types of interface devices), a memory 140, and/orone or more applications 126. In some implementations, a copy of thehypothesis 60 and/or a copy of a modified hypothesis 80 may be stored inmemory 140. The one or more applications 126 may include one or morecommunication applications 267 (e.g., email application, IM application,text messaging application, a voice recognition application, and soforth) and/or one or more Web 2.0 applications 268. Note that in variousembodiments, a persistent copy of the one or more applications 126 maybe stored in memory 140.

Turning now to FIG. 2 a illustrating particular implementations of thehypothesis presentation module 102 of FIG. 1 b. The hypothesispresentation module 102 may be configured to present one or morehypotheses 60 including presenting to a user 20* a hypothesis 60identifying at least a relationship between at least a first event type(e.g., a subjective user state, a subjective observation, or anobjective occurrence) and a second event type (e.g., a subjective userstate, a subjective observation, or an objective occurrence). Note thatin embodiments in which the computing device 10 is a server, thehypothesis 60 to be presented may be presented to user 20 a bytransmitting the hypothesis 60 to a mobile device 30, which may thenaudioally or visually indicate the hypothesis 60 to user 20 a. While inembodiments in which the computing device 10 is a standalone device, thecomputing device 10 may present the hypothesis 60 to a user 20 b via theuser interface 122.

In some implementations, the hypothesis 60 to be presented may identifythe relationships between the first, the second event type, a thirdevent type, a fourth event type, and so forth. As will be furtherdescribed herein, the hypothesis 60 to be presented by the hypothesispresentation module 102 may identify the relationship between a varietyof different event types (e.g., identifying a relationship between asubjective user state and an objective occurrence, identifying arelationship between a first objective occurrence and a second objectiveoccurrence, and so forth). In some implementations, the hypothesis 60 tobe presented may have been previously developed based on data providedby the user 20*. In the same or different implementations, thehypothesis 60 to be presented may be related to the user 20*, to one ormore third parties 50, to one or more devices, or to one or moreenvironmental characteristics or conditions.

In order to present a hypothesis 60, the hypothesis presentation module102 may further include one or more sub-modules. For instance, invarious implementations, the hypothesis presentation module 102 mayinclude a network transmission module 202 configured to transmit thehypothesis 60 to a user 20 a via at least one of a wireless network anda wired network (e.g., wireless and/or wired network 40).

In the same or different implementations, the hypothesis presentationmodule 102 may include a user interface indication module 204 configuredto indicate the hypothesis 60 to a user 20 b via a user interface 122(e.g., an audio system including one or more speakers and/or a displaysystem including a display monitor or touchscreen). The user interfaceindication module 204 may, in turn, further include one or moreadditional sub-modules. For example, in some implementations, the userinterface indication module 204 may include an audio indication module206 configured to audioally indicate the hypothesis 60 to user 20 b.

In the same or different implementations, the user interface indicationmodule 204 may include a visual indication module 208 configured tovisually indicate the hypothesis 60 to user 20 b. Note that, and as willbe further described herein, the visual indication module 208 mayvisually indicate the hypothesis 60 in a variety of different mannersincluding, for example, in graphical form, in textual form, in pictorialform, and so forth. Further, in various implementations, the visualindication module 208 may represent the various event types and theirrelationships with respect to each other as indicated by the hypothesis60 by symbolic representations (see, for example, FIGS. 2 h to 2 k).

For example, the visual indication module 208 indicating visually to theuser 20* symbolic representations that may represent the various eventtypes indicated by the hypothesis 60 including, for example, a firstsymbolic representation representing the first event type, a secondsymbolic representation representing the second event type, a thirdsymbolic representation representing a third event type, a fourthsymbolic representation representing a fourth event type, and so forth.A symbolic representation may be, for example, an icon, an emoticon, afigure, text such as a word or phrase, and so forth. Similarly, thevisual indication module 208 may indicate the relationships (e.g.,spatial or temporal relationships) between the event types, asidentified by the hypothesis 60, by visually indicating symbolicrepresentations that represents the relationships between the eventtypes. Such symbolic representations representing the relationshipsbetween the event types may include, for example, specific spacing orangle between the symbolic representations representing the event types(e.g., as set against a grid background), lines or arrows between thesymbolic representations representing the event types, text including aword or phrase, and/or a combination thereof.

In some implementations, the visual indication module 208 may furtherinclude a visual attribute adjustment module 210 that is configured toindicate the strength of the hypothesis 60 by adjusting a visualattribute (e.g., boldness, color, background, and so forth) associatedwith at least one of the symbolic representations representing the eventtypes and their relationships. In various implementations, thehypothesis presentation module 102 may include an editable hypothesispresentation module 212 configured to present an editable form of thehypothesis 60 to the user 20*. In some embodiments, the editable form ofthe hypothesis 60 to be presented by the editable hypothesispresentation module 212 may include symbolic representationsrepresenting the event types and their relationships with respect toeach other that may be modified and/or deleted. In the same or differentimplementations, the editable form of the hypothesis 60 may be modifiedsuch that additional event types may be added with respect to the eventtypes already identified by the hypothesis 60.

In some implementations, the hypothesis presentation module 102 of FIG.2 a may include a hypothesis deletion option presentation module 214configured to present an option to delete the hypothesis 60. In the sameor alternative implementations, the hypothesis presentation module 102may include a hypothesis deactivation option presentation module 216configured to present an operation to deactivate or ignore thehypothesis 60. By deactivating the hypothesis 60, the action executionmodule 108 of the computing device 10 may be prevented from executingone or more actions based on the hypothesis 60 (e.g., or a modifiedversion of the hypothesis 60).

Turning now to FIG. 2 b illustrating particular implementations of themodification reception module 104 of FIG. 1 b. In variousimplementations, the modification reception module 104 may be configuredto receive at least one modification 61 to modify the hypothesis 60 fromthe user 20*. The modification reception module 104 may include one ormore sub-modules in various alternative implementations. For example, insome implementations such as in implementations in which the computingdevice 10 is a standalone device, the modification reception module 104may include a user interface reception module 218 configured to receivethe at least one modification 61 for modifying the hypothesis 60 througha user interface 122 (e.g., a key pad, a microphone, a touchscreen, amouse, a keyboard, and so forth). In the same or differentimplementations such as in implementations in which the computing device10 is a server, the modification reception module 104 may include anetwork reception module 220 configured to receive the at least onemodification 61 for modifying the hypothesis 60 via at least one of awireless and/or wired network 40.

As depicted in FIG. 2 b, the modification reception module 104 mayinclude, in various implementations, an electronic entry receptionmodule 222 configured to receive (e.g., via a user interface 122 or viawireless and/or wired network 40) the at least one modification 61 tomodify the hypothesis 60 via one or more electronic entries as providedby the user 20*. In some implementations, the electronic entry receptionmodule 222 may further include one or more sub-modules including, forexample, a blog entry reception module 224 (e.g., for receiving from theuser 20* the at least one modification 61 via one or more blog ormicroblog entries), a status report reception module 226 (e.g., forreceiving from the user 20* the at least one modification 61 via one ormore social networking status reports), an electronic message receptionmodule 228 (e.g., for receiving from the user 20* the at least onemodification 61 via one or more electronic messages such as e.g.,emails, text messages, instant messages (IMs), and so forth), and/or adiary entry reception module 230 (e.g., for receiving from the user 20*the at least one modification 61 via one or more diary entries).

Various types of modifications 61 for modifying the hypothesis 60 may bereceived by the modification reception module 104. For instance, in someimplementations, modifications 61 for deleting one or more of the eventtypes (e.g., the first event type, the second event type, and so forth)indicated by the hypothesis 60 may be received by the modificationreception module 104. For example, the modification reception module 104may receive one or more modifications 61 for deleting a third eventtype, a fourth event type, and so forth, indicated by the hypothesis 60.

In some implementations, the modification reception module 104 may bedesigned to receive one or more modifications 61 for adding additionalevent types (e.g., a third event type, a fourth event type, and soforth) to the hypothesis 60 and with respect to the at least first eventtype and the second event type already included in the hypothesis 60.Note that when adding a new event type to the hypothesis 60, therelationships (e.g., spatial or temporal) between the added event type(e.g., a third event type) and the first event type and the second eventtype may also be provided.

In some implementations, the modification reception module 104 may bedesigned to receive one or more modifications 61 for revising one ormore of the event types (e.g., the first event type and the second eventtype) included in the hypothesis 60. In the same or differentimplementations, the modification reception module 104 may be configuredto receive one or more modifications 61 for modifying (e.g., revising)the relationship or relationships (e.g., spatial, temporal, or specifictime relationship) between the event types (e.g., the first event type,the second event type, and so forth) included in the hypothesis 60. Theone or more modifications 61 to be received by the modificationreception module 104 may be for modifying any type of event typesincluding, for example, a subjective user state type, a subjectiveobservation type, and/or an objective occurrence type.

In various implementations, the computing device 10 may include ahypothesis modification module 106 that is designed to modify thehypothesis 60 based, for example, on the one or more modifications 61received by the modification reception module 104. As a result ofmodifying the hypothesis 60, a modified hypothesis 80 may be generated,which in some cases may be stored in memory 140.

FIG. 2 c illustrates particular implementations of the action executionmodule 108 of FIG. 1 b. The action execution module 108 may be designedto execute at least one action based, at least in part, on a modifiedhypothesis 80 generated as a result, at least in part, of the receptionof the at least one modification 61 by the modification reception module104. As depicted in FIG. 2 c, the action execution module 108 mayinclude an advisory presentation module 232 that may be configured topresent (e.g., indicate via user interface 122 or transmit via wirelessand/or wired network 40) at least one advisory 90 related to themodified hypothesis 80. In various implementations, the at least oneadvisory 90 may be presented to a user 20* and/or one or more thirdparties 50.

The advisory presentation module 232 may further include one or moresub-modules in various alternative implementations. For instance, invarious implementations, the advisory presentation module 232 mayinclude a user interface indication module 234 that is configured toindicate the at least one advisory 90 via a user interface 122. In thesame or different implementations, the advisory presentation module 232may include a network transmission module 236 configured to transmit theat least one advisory 90 via a wireless and/or wired network 40. Thenetwork transmission module 236 may transmit the at least one advisory90 to, for example, a user 20 a (e.g., via mobile device 30) and/or oneor more third parties 50.

In the same or different implementations, the advisory presentationmodule 232 may include a modified hypothesis presentation module 238configured to present one or more form of the modified hypothesis 80.For instance, presenting an audio form, a textual form, a pictorialform, a graphical form, and/or other forms of the modified hypothesis80. The modified hypothesis presentation module 238 may present the atleast one form of the modified hypothesis 80 by presenting an indicationof a spatial, temporal, or specific time relationship between at leasttwo event types indicated by the modified hypothesis 80. The at leastone form of the modified hypothesis 80 presented by the modifiedhypothesis presentation module 238 may indicate the relationship betweenthe event types indicated by the modified hypothesis 80 including anycombination of subjective user state types, objective occurrence types,and/or subjective observation types (e.g., indicate a relationshipbetween a first type of subjective user state and a second type ofsubjective user state, indicate a relationship between a type ofsubjective user state and a type of objective occurrence, indicate arelationship between a type of subjective user state and a type ofsubjective observation, and so forth) as indicated by the modifiedhypothesis 80.

The advisory presentation module 232 may further include othersub-modules in various implementations. For example, in someimplementations, the advisory presentation module 232 may include aprediction presentation module 240 configured to present at least oneadvisory 90 relating to a predication of one or more future eventsbased, at least in part, on the modified hypothesis 80. For example,predicting that “a personal passenger vehicle belonging to the user willbreakdown sometime during the coming week.”

In various implementations, the advisory presentation module 232 mayinclude a recommendation presentation module 242 configured to presentat least one advisory 90 recommending a future course of action based,at least in part, on the modified hypothesis 80. For example,recommending that “the user take his personal passenger vehicle into theshop for repairs.” In some implementations, the recommendationpresentation module 242 may include a justification presentation module244 configured to present a justification for the recommendationpresented by the recommendation presentation module 242. For example,indicating that “the user should take her personal passenger vehicleinto the shop because the last time the user did not take her personalvehicle into the shop after driving it for 15 thousand miles withoutbeing serviced, the personal vehicle broke down.”

In some implementations, the advisory presentation module 232 mayinclude a past event presentation module 246 configured to present anindication of one or more past events based, at least in part, on themodified hypothesis 80 (e.g., “the last time your husband went drinking,he overslept”).

In various implementations, the action execution module 108 may includea device prompting module 248 configured to prompt (e.g., as indicatedby ref. 91) at least one devices to execute at least one operationbased, at least in part, on the modified hypothesis 80. The at least onedevice to be prompted to execute the at least one operation may include,for example, one or more sensing devices 35*, or one or morenetwork/local devices 55. Network/local devices 55 are any device thatmay interface with a wireless and/or wired network 40 and/or any devicethat may be local with respect to, for example, the computing device 10.Examples of network/local devices 55 includes, for example, householddevices such as household appliances, automobiles (or portions thereof),environmental devices such as air conditioners, humidifier, airpurifiers, and so forth, electronic/communication devices (e.g., mobiledevice 30), and so forth.

In various alternative implementations, the device prompting module 248may include one or more sub-modules. For example, in someimplementations, the device prompting module 248 may include a deviceinstruction module 250 configured to directly or indirectly instruct theat least one device (e.g., directly instructing a local device orindirectly instructing a network device via wireless and/or wirednetwork 40) to execute the at least one operation. In the same ordifferent implementations, the device prompting module 248 may include adevice activation module 252 configured to directly or indirectlyactivate the at least one device (e.g., directly activating a localdevice or indirectly activating a network device via wireless and/orwired network 40) to execute the at least one operation. In the same ordifferent implementations, the device prompting module 248 may include adevice configuration module 254 designed to directly or indirectlyconfigure the at least one device (e.g., directly configuring a localdevice or indirectly configuring a network device via wireless and/orwired network 40) to execute the at least one operation.

Referring back to the action execution module 108 of FIGS. 1 b and 2 c,in various implementations, the action execution module 108 may beconfigured to execute the one or more actions based on the modifiedhypothesis 80 as generated by the hypothesis modification module 106 andin response to a reported event. For example, the one or more actionsmay be executed if the reported event at least substantially matcheswith at least one of the event types (e.g., substantially matches withat least one of at least two event types) identified by the modifiedhypothesis 80. In some specific implementations, the one or more actionsmay only be executed if the reported event matches at least one of theevent types identified by the modified hypothesis 80.

In various implementations, the computing device 10 of FIG. 1 b mayinclude one or more applications 126. The one or more applications 126may include, for example, one or more communication applications 267(e.g., text messaging application, instant messaging application, emailapplication, voice recognition system, and so forth) and/or Web 2.0application 268 to facilitate in communicating via, for example, theWorld Wide Web. In some implementations, copies of the one or moreapplications 126 may be stored in memory 140.

In various implementations, the computing device 10 may include anetwork interface 120, which may be a device designed to interface witha wireless and/or wired network 40. Examples of such devices include,for example, a network interface card (NIC) or other interface devicesor systems for communicating through at least one of a wireless networkor wired network 40. In some implementations, the computing device 10may include a user interface 122. The user interface 122 may compriseany device that may interface with a user 20 b. Examples of such devicesinclude, for example, a keyboard, a display monitor, a touchscreen, amicrophone, a speaker, an image capturing device such as a digital orvideo camera, a mouse, and so forth.

The computing device 10 may include a memory 140. The memory 140 mayinclude any type of volatile and/or non-volatile devices used to storedata. In various implementations, the memory 140 may comprise, forexample, a mass storage device, a read only memory (ROM), a programmableread only memory (PROM), an erasable programmable read-only memory(EPROM), random access memory (RAM), a flash memory, a synchronousrandom access memory (SRAM), a dynamic random access memory (DRAM),and/or other memory devices. In various implementations, the memory 140may store an existing hypotheses 80 and/or historical data (e.g.,historical data including, for example, past events data or historicalevents patterns related to a user 20*, related to a subgroup of thegeneral population that the user 20* belongs to, or related to thegeneral population).

FIG. 2 d illustrates particular implementations of the mobile device 30of FIG. 1 a. The mobile device 30, as previously described, may be alarger computing/communication device such as a laptop or a desktopcomputer, or a smaller computing/communication device including ahandheld device such as a cellular telephone, a smart phone, a PDA, andso forth. In various embodiments, the mobile device 30 may includecomponents and modules similar to those included in the computing device10 of FIG. 1 b.

For example, and similar to the computing device 10, the mobile device30 may also include a hypothesis presentation module 102′, amodification reception module 104′, an action execution module 108′, areported event reception module 110′, a network interface 120′, a userinterface 122′, a memory 140′, and/or one or more applications 126′,which may include one or more communication applications 267′ and/or oneor more Web 2.0 applications 268′. Note that in some implementations,memory 140′ may store a copy of the hypothesis 60 and/or the modifiedhypothesis 80′. These components and modules may generally perform thesame or similar functions as their counterparts in the computing device10 the computing device 10 with certain exceptions. For instance, withrespect to the hypothesis presentation modules 102* of the mobile device30 and the computing device 10, in the mobile device 30 case thehypothesis presentation module 102′ may present (e.g., audioally orvisually indicate) a hypothesis 60 to a user 20 a via a user interface122′ while in the computing device 10 the hypothesis presentation module102 may present a hypothesis 60 to a user 20 a by transmitting thehypothesis 60 to the mobile device 30 via wireless and/or wired network40 (e.g., in embodiments in which the computing device 10 is a server)or may present (e.g., audioally or visually indicate) the hypothesis 60to a user 20 b via a user interface 122 (e.g., in embodiments in whichthe computing device 10 is a standalone device). Note also that theunlike the computing device 10, the mobile device 30 may not include ahypothesis modification module 106 or a hypothesis development module112 since operations performed by such modules may be performed by, forexample, a server (e.g., computing device 10 in embodiments in which thecomputing device 10 is a server).

In addition to those components and modules described above, the mobiledevice 30 may include a modification transmission module 219 and anadvisory reception module 235. The modification transmission module 219may be designed to, among other things, transmit one or moremodifications 61 (e.g., as provided by a user 20 a through userinterface 122′) to a server (e.g., computing device 10 in embodiments inwhich the computing device 10 is a server) via, for example, wirelessand/or wired network 40. The advisory reception module 235 may bedesigned to receive one or more advisories 90 related to the modifiedhypothesis 80 from the computing device 10 via, for example, wirelessand/or wired network 40, the modified hypothesis 80 being generated bythe computing device 10 (e.g., in embodiments in which the computingdevice 10 is a server) based on the hypothesis 60 and the one or moremodifications 61 received from the mobile device 30.

FIG. 2 e illustrates particular implementations of the hypothesispresentation module 102′ of the mobile device 30 of FIG. 2 d. Thehypothesis presentation module 102′ of the mobile device 30 may performthe same or similar functions (e.g., present one or more hypothesesincluding presenting to a user 20 a a hypothesis 60) as the hypothesispresentation module 102 of the computing device 10 (e.g., in embodimentsin which the computing device 10 is a standalone device). Asillustrated, the hypothesis presentation module 102′ may include a userinterface indication module 204′, an editable hypothesis presentationmodule 212′, a hypothesis deletion option presentation module 214′,and/or a hypothesis deactivation option presentation module 216′. Invarious implementations, the user interface indication module 204′ mayfurther include an audio indication module 206′ and a visual indicationmodule 208′, which may further include a visual attribute adjustmentmodule 210′. These modules corresponds to and may perform the same orsimilar functions as the user interface indication module 204 (which mayinclude the audio indication module 206, the visual indication module208, and the visual attribute adjustment module 210), the editablehypothesis presentation module 212, the hypothesis deletion optionpresentation module 214, and the hypothesis deactivation optionpresentation module 216 (see FIG. 2 a), respectively, of computingdevice 10.

FIG. 2 f illustrates particular implementations of the modificationreception module 104′ of the mobile device 30 of FIG. 2 d. In variousimplementations, the modification reception module 104′ may perform thesame or similar functions (e.g., to receive at least one modification 61to modify the hypothesis 60 from the user 20 a) as the modificationreception module 104 of the computing device 10 (e.g., in embodiments inwhich the computing device 10 is a standalone device). As illustrated,the modification reception module 104′ may include a user interfacereception module 218′ and an electronic entry reception module 222′,which may further include a blog entry reception module 224′, a statusreport reception module 226′, electronic message reception module 228′,and/or diary entry reception module 230′. These modules may correspondto and may perform the same or similar functions as the functionsperformed by the user interface reception module 218, the electronicentry reception module 222, the blog entry reception module 224, thestatus report reception module 226, the electronic message receptionmodule 228, and the diary entry reception module 230 (see FIG. 2 b),respectively, of the computing device 10.

FIG. 2 g illustrates particular implementations of the action executionmodule 108′ of the mobile device 30 of FIG. 2 d. In variousimplementations, the action execution module 108′ may perform the sameor similar functions (e.g., executing one or more actions based, atleast in part, on a modified hypothesis 80 resulting, at least in part,from the reception of the one or modifications 61 by the modificationreception module 104′) as the action execution module 108 of thecomputing device 10 (e.g., in embodiments in which the computing device10 is a standalone device). As illustrated, the action execution module108′ may include an advisory presentation module 232′ and a deviceprompting module 248′ that corresponds to and performs the same orsimilar functions as the advisory presentation module 232 and the deviceprompting module 248 of the computing device 10. As further illustrated,the advisory presentation module 232′ may further include the same oneor more sub-modules (e.g., a user interface indication module 234′, anetwork transmission module 236′, a modified hypothesis presentationmodule 238′, a prediction presentation module 240′, a recommendationpresentation module 242′ that further includes a justificationpresentation module 244′, and/or a justification presentation module244′) that may be included in the advisory presentation module 232 ofthe computing device 10 performing the same or similar functions astheir counterparts in the computing device 10. Likewise, the deviceprompting module 248′ may further include the same one or moresub-modules (e.g., a device instruction module 250′, a device activationmodule 252′, and/or a device configuration module 254′) that may beincluded in the device prompting module 248 of the computing device 10performing the same or similar functions as their counterparts in thecomputing device 10.

There are many ways that a hypothesis 60 (or a modified hypothesis 80)may be visually or audioally indicated to a user 20*. FIGS. 2 h to 2 killustrates just a few examples of how a hypothesis 60 (or a modifiedhypothesis 80) may be visually indicated on a user interface displaydevice such as a display monitor or touchscreen. In particular, FIG. 2 his an exemplary textual version of a hypothesis 60 being visuallyindicated on a user interface display 270. The user interface display270 shows a textual message indicating the hypothesis 60. In this case,some groups of words within the message represent different event types,while other words in the message represent the temporal relationshipsbetween the event types. For example, refs. 271, 272, 273, and 274indicate selective words in the textual message that are differentsymbolic representations of different event types (e.g., waking up late,eating ice cream, drinking coffee, and stomachache). Refs. 275 a, 275 b,and 275 c indicate symbolic representations (e.g., in the form of words)that represents the relationships (e.g., sequential or temporalrelationships) between the different event types represented on the userinterface display 270.

FIG. 2 i is an exemplary pictorial version of the hypothesis 60textually illustrated in FIG. 2 h being pictorially indicated on a userinterface display 276. The user interface display 276 shows multiplesymbolic representations (refs. 277, 278, 279, 280, 281 a, 281 b, and281 c) in the form of emoticons and figures/icons that represents thedifferent event types and their relationships with each other. Forinstance, in this example the symbolic representation 277 (in the formof an emoticon) represents the event type “waking up late.” The symbolicrepresentation 278 (in the form of a figure/icon) represents the eventtype “eating ice cream.” The symbolic representation 279 (in the form ofa figure/icon) represents the event type “drinking coffee.” The symbolicrepresentation 280 (in the form of an emoticon) represents the eventtype “stomachache.” The symbolic representations 281 a, 281 b, and 281 c(in the form of arrows) represents the temporal relationships betweenthe event types (e.g., as represented by symbolic representations 277,278, 279, and 280) represented on the user interface display 276.

FIG. 2 j is another exemplary pictorial version of the hypothesis 60that was textually illustrated in FIG. 2 h being again pictoriallyindicated on a user interface display 284. The user interface display284 shows oval shapes (symbolic representations 285, 286, 287, and 288)that represents the four different event types. The relationships (e.g.,temporal relationships) between the four different event types (asrepresented by the symbolic representations 285, 286, 287, and 288) maybe symbolically represented by the specific placement of the symbolicrepresentations 285, 286, 287, and 288 with respect to the userinterface display 284 and with respect to each other. For example, inthis illustrated example the top left corner of the user interfacedisplay may represent the earliest point in time, while the bottom rightcorner may represent the latest point in time. Thus, symbolicrepresentation 285 (e.g., representing “wake up late”) being closest tothe top left corner of the user interface display 284 represents theearliest event type to occur, while symbolic representation 288 (e.g.,representing “stomach ache”), which is located nearest to the bottomright corner, represents the latest event type to occur. Note thatsymbolic representation 286 and symbolic representation 287 intersecteach other. Thus, the event types (e.g., “eat ice cream” and “drinkcoffee”) that they represent are at least partially concurrentlyoccurring event types. In order to facilitate a user in understandingthe time relationships between the different event types a timeincrement grid may be placed in the background.

FIG. 2 k illustrates a pictorial/graphical representation of ahypothesis 60 (e.g., a hypothesis 60 that links going to work, arrivingat work, drinking coffee, learning boss plans to leave town, bossleaving town, and overall user state) being pictorially/graphicallyrepresented on a user interface display 290. In this example, most ofthe event types indicated by the hypothesis 60 are represented by blocks(e.g., symbolic representations 291 a, 291 b, 291 c, 291 d, and 291 e)below a timeline. The overall user state is represented symbolically bya line to indicate the specific overall user state at any given momentin time. Note that by employing the robust systems and methods describedherein, a user may be able to modify the hypothesis 60 depicted in theuser interface display 290. That is, the user may choose to modify thehypothesis 60 by deleting symbolic representations 291 a, 291 b, and 291c (e.g., representing going to work, arriving at work, and drinkingcoffee) if the user feels that the events represented by the symbolicrepresentations may not be relevant to the user having a very goodoverall user state.

The various features and characteristics of the components, modules, andsub-modules of the computing device 10 and mobile device 30 presentedthus far will be described in greater detail with respect to theprocesses and operations to be described herein.

FIG. 3 illustrates an operational flow 300 representing exampleoperations related to, among other things, presenting a hypothesis to auser that identifies at least a relationship between a first event typeand a second event type, receiving one or more modifications to modifythe hypothesis from the user, and executing one or more actions based,at least in part, on a modified hypothesis resulting at least in partfrom the reception of the one or more modifications. In someembodiments, the operational flow 300 may be executed by, for example,the mobile device 30 or the computing device 10 of FIGS. 1 a and 1 b.

In FIG. 3 and in the following figures that include various examples ofoperational flows, discussions and explanations may be provided withrespect to the above-described exemplary environment of FIGS. 1 a and 1b, and/or with respect to other examples (e.g., as provided in FIGS. 2a-2 k) and contexts. However, it should be understood that theoperational flows may be executed in a number of other environments andcontexts, and/or in modified versions of FIGS. 1 a, 1 b, and 2 a-2 k.Also, although the various operational flows are presented in thesequence(s) illustrated, it should be understood that the variousoperations may be performed in different sequential orders other thanthose which are illustrated, or may be performed concurrently.

Further, in the following figures that depict various flow processes,various operations may be depicted in a box-within-a-box manner. Suchdepictions may indicate that an operation in an internal box maycomprise an optional example embodiment of the operational stepillustrated in one or more external boxes. However, it should beunderstood that internal box operations may be viewed as independentoperations separate from any associated external boxes and may beperformed in any sequence with respect to all other illustratedoperations, or may be performed concurrently.

In any event, after a start operation, the operational flow 300 may moveto a hypothesis presentation operation 302 for presenting to a user ahypothesis identifying at least a relationship between a first eventtype and a second event type. For instance, the hypothesis presentationmodule 102* of the mobile device 30 or the computing device 10presenting (e.g., indicating via a user interface 122* or transmittingvia wireless and/or wired network 40) to a user 20* a hypothesis 60identifying at least a relationship between a first event type (e.g., asubjective user state, a subjective observation, or an objectiveoccurrence) and a second event type (e.g., a subjective user state, asubjective observation, or an objective occurrence).

Next, operational flow 300 may include a modification receptionoperation 304 for receiving from the user one or more modifications tomodify the hypothesis. For instance, the modification reception module104* of the mobile device 30 or the computing device 10 receiving (e.g.,receiving via a user interface 122 or via wireless and/or wired network40) from the user 20* one or more modifications 61 to modify thehypothesis 60.

Finally, operation flow 300 may include an action execution operation306 for executing one or more actions based, at least in part, on amodified hypothesis resulting, at least in part, from the reception ofthe one or more modifications. For instance, the action execution module108* of the mobile device 30 or the computing device 10 executing one ormore actions (e.g., presenting one or more advisories 90 or configuringa device to execute one or more operations) based, at least in part, ona modified hypothesis 80 resulting, at least in part, from the receptionof the one or more modifications 61. In a more specific example, theaction execution module 108′ of the mobile device 30 executing one ormore actions (e.g., displaying the modified hypothesis 80 or prompting91′ one or more devices such as one or more sensing devices 35* ornetwork/local devices 55 to execute one or more operations) afterreceiving from the computing device 10 (e.g., when the computing device10 is a server) a request for executing the one or more actions. In thisexample, the request may have been generated and transmitted by thecomputing device 10 based, at least in part, on the modified hypothesis80.

Referring back to the hypothesis presentation operation 302, thehypothesis 60 presented through the hypothesis presentation operation302 may be presented in a variety of different ways. For example, insome implementations, the hypothesis presentation operation 302 mayinclude an operation 402 for transmitting to the user, via at least oneof a wireless network and a wired network, the hypothesis as depicted inFIG. 4 a. For instance, the network transmission module 202 (see FIG. 2a) of the computing device 10 (e.g., in embodiments in which thecomputing device 10 is a server) transmitting to the user 20 a, via atleast one of a wireless network and a wired network 40, the hypothesis60.

In some alternative implementations, the hypothesis presentationoperation 302 may include an operation 403 for indicating to the user,via a user interface, the hypothesis as depicted in FIG. 4 a. Forinstance, the user interface indication module 204* of the mobile device30 or the computing device 10 (e.g., in embodiments in which thecomputing device 10 is a standalone device) indicating to the user 20*,via a user interface 122*, the hypothesis 60.

In some implementations, operation 403 may include an operation 404 forindicating audioally to the user the hypothesis as depicted in FIG. 4 a.For instance, the audio indication module 206* of the mobile device 30or the computing device 10 (e.g., in embodiments in which the computingdevice 10 is a standalone device) indicating audioally (e.g., viaspeaker system) to the user 20* the hypothesis 60.

In the same or different implementations, operation 403 may include anoperation 405 for indicating visually to the user the hypothesis asdepicted in FIG. 4 a. For instance, the visual indication module 208* ofthe mobile device 30 or the computing device 10 (e.g., in embodiments inwhich the computing device 10 is a standalone device) indicatingvisually (e.g., via a display device such as a display monitor ortouchscreen) to the user 20* the hypothesis 60.

In some implementations, operation 405 may further include an operation406 for indicating visually to the user the hypothesis via a displayscreen as depicted in FIG. 4 a. For instance, the visual indicationmodule 208* of the mobile device 30 or the computing device 10indicating visually to the user 20* the hypothesis 60 via a displayscreen (e.g., touchscreen).

The hypothesis 60 to be visually indicated through operation 405 may beindicated in a variety of ways including, for example, in text form, ingraphical form, in pictorial form, and so forth. For example, in variousimplementations, operation 405 may include an operation 407 forindicating visually to the user a first symbolic representationrepresenting the first event type and a second symbolic representationrepresenting the second event type as depicted in FIG. 4 a. Forinstance, the visual indication module 208* of the mobile device 30 orthe computing device 10 indicating visually to the user 20* a firstsymbolic representation representing the first event type and a secondsymbolic representation representing the second event type. A symbolicrepresentation may be, for example, an icon, an emoticon, a figure,text, a number, and so forth.

In some implementations, operation 407 may further include an operation408 for indicating visually to the user a third symbolic representationrepresenting the relationship between the first event type and thesecond event type as depicted in FIG. 4 a. For instance, the visualindication module 208* of the mobile device 30 or the computing device10 indicating visually to the user 20* a third symbolic representationrepresenting the relationship between the first event type and thesecond event type. For example, in some implementations, the thirdsymbolic representation may be the spacing between the first and secondsymbolic representations shown on a display screen, a line or an arrowbetween the first and second symbolic representations, an attribute suchas the color or darkness associated with the first and second symbolicrepresentations, a textual phrase, and so forth.

Operation 408 may include, in various implementations, an operation 409for adjusting a visual attribute associated with at least one of thefirst symbolic representation, the second symbolic representation, andthe third symbolic representation to indicate strength of the hypothesisas depicted in FIG. 4 a. For instance, the visual attribute adjustmentmodule 210* of the mobile device 30 or the computing device 10 adjustinga visual attribute (e.g., adjusting boldness, highlighting, color,spacing or angular relationships between the symbols, and so forth)associated with at least one of the first symbolic representation, thesecond symbolic representation, and the third symbolic representation toindicate strength of the hypothesis 60. In some implementations, thestrength of a hypothesis 60 may be related to confidence level of thehypothesis 60. For instance, a hypothesis 60 that was developed based ona relatively large pool of data that shows a pattern of reported eventsthat have repeatedly occurred and that uniformly supports the hypothesis60 would result in a stronger or sounder hypothesis 60.

In some alternative implementations, operation 408 may include anoperation 410 for indicating visually to the user a fourth symbolicrepresentation representing strength of the hypothesis as depicted inFIG. 4 a. For instance, the visual indication module 208* of the mobiledevice 30 or the computing device 10 indicating visually to the user 20*a fourth symbolic representation (e.g., a number) representing strength(e.g., soundness) of the hypothesis 60.

In various implementations, operation 407 may include an operation 411for indicating visually to the user a first icon representing the firstevent type and a second icon representing the second event type asdepicted in FIG. 4 a. For instance, the visual indication module 208* ofthe mobile device 30 or the computing device 10 indicating visually tothe user 20* a first icon (e.g., an emoticon such as a smiling face)representing the first event type (e.g., happiness) and a second icon(e.g., a figure of the sun) representing the second event type (e.g.,sunny weather).

In alternative implementations, operation 407 may include an operation412 for indicating visually to the user a first textual representationrepresenting the first event type and a second textual representationrepresenting the second event type as depicted in FIG. 4 b. Forinstance, the visual indication module 208* of the mobile device 30 orthe computing device 10 indicating visually to the user 20* a firsttextual representation (e.g., “sadness”) representing the first eventtype and a second textual representation (e.g., “overcast day”)representing the second event type.

Operation 412, in turn, may include an operation 413 for indicatingvisually to the user a textual passage including the first and secondtextual representations, the textual passage representing therelationship between the first event type and the second event type asdepicted in FIG. 4 b. For instance, the visual indication module 208* ofthe mobile device 30 or the computing device 10 indicating visually tothe user 20* a textual passage including the first and second textualrepresentations, the textual passage representing the relationshipbetween the first event type and the second event type (e.g., “wheneverit is cloudy, you are sad”).

In various implementations, the hypothesis presentation operation 302 ofFIG. 3 may include an operation 414 for presenting to the user aneditable form of the hypothesis as depicted in FIG. 4 c. For instance,the editable hypothesis presentation module 212* of the mobile device 30or the computing device 10 presenting to the user 20* an editable formof the hypothesis 60. For example, in embodiments where the computingdevice 10 is a server that communicates with a user 20 a via the mobiledevice 30, the editable hypothesis presentation module 212 of thecomputing device 10 may be designed to present an editable version ofthe hypothesis 60 to the user 20 a by transmitting the editable versionof the hypothesis 60 to the mobile device 30. The editable hypothesispresentation module 212′ of the mobile device 30 may then present theeditable version of the hypothesis 60 to the user 20 a by indicating theeditable version of the hypothesis 60 via a user interface 122′ (e.g., aspeaker system and/or a display system). The modifications made by theuser 20 a may then be transmitted back to the computing device 10 formodifying the hypothesis 60

As further depicted in FIG. 4 c, in some implementations, operation 414may include an operation 415 for presenting to the user an editable formof the hypothesis including at least a first editable symbolicrepresentation representing the first event type and a second editablesymbolic representation representing the second event type. Forinstance, the editable hypothesis presentation module 212* of the mobiledevice 30 or the computing device 10 presenting (e.g., audioally orvisually indicating or transmitting via a wireless and/or wired network40) to the user 20* an editable form of the hypothesis 60 including atleast a first editable (e.g., deletable and/or modifiable) symbolicrepresentation representing the first event type and a second editable(e.g., deletable and/or modifiable) symbolic representation representingthe second event type.

Operation 415 may, in turn, comprise one or more additional operationsin various alternative implementations. For example, in someimplementations, operation 415 may include an operation 416 forpresenting to the user an editable form of the hypothesis including atleast a first deletable symbolic representation representing the firstevent type and a second deletable symbolic representation representingthe second event type as depicted in FIG. 4 c. For instance, theeditable hypothesis presentation module 212* of the mobile device 30 orthe computing device 10 presenting (e.g., audioally or visuallyindicating or transmitting via a wireless and/or wired network 40) tothe user 20* an editable form of the hypothesis 60 including at least afirst deletable symbolic representation representing the first eventtype and a second deletable symbolic representation representing thesecond event type.

As a further illustration, suppose the user 20* is presented with theeditable form of the hypothesis 60 that may have been previouslydeveloped based on events previously reported by the user 20* thatindicates that the user 20* may get a stomach ache (e.g., a first eventtype) if the user 20* eats at a particular Mexican restaurant (e.g., asecond event type). After being presented with the editable form of thehypothesis 60, the user 20* recognizes that the hypothesis 60 may havebeen based solely on the user 20* last reported visit to that particularrestaurant when the user 20* got sick and now realizes that the cause ofhis stomach ache may not have been from the visit to that particularrestaurant but rather eating a new dish containing a new ingredient hehad never eaten before. Thus, the user 20* may want to modify theeditable form of the hypothesis 60 to delete one of the event typesidentified by the hypothesis 60 (e.g., the second symbolicrepresentation representing the second event type that indicates eatingat the particular Mexican restaurant) and replacing the deleted eventtype (or the second symbolic representation) with a new event type(e.g., a third symbolic representation representing the consumption ofthe new dish containing the new ingredient).

In some implementations, operation 415 may include an operation 417 forpresenting to the user an editable form of the hypothesis including atleast a first modifiable symbolic representation representing the firstevent type and a second modifiable symbolic representation representingthe second event type as depicted in FIG. 4 c. For instance, theeditable hypothesis presentation module 212* of the mobile device 30 orthe computing device 10 presenting (e.g., audioally or visuallyindicating or transmitting) to the user 20* an editable form of thehypothesis 60 including at least a first modifiable symbolicrepresentation (e.g., a smiling face emoticon) representing the firstevent type and a second modifiable symbolic representation (e.g., apicture of clouds) representing the second event type. Such a feature(e.g., providing modifiable symbolic representations) may allow the user20* to, for example, correct the hypothesis 60 (e.g., changing a smilingface emoticon to a sad face emoticon).

In some implementations, operation 415 may include an operation 418 forpresenting to the user an editable form of the hypothesis including atleast an editable symbolic representation representing the relationshipbetween the first event type and the second event type as depicted inFIG. 4 c. For instance, the editable hypothesis presentation module 212*of the mobile device 30 or the computing device 10 presenting (e.g.,audioally or visually indicating or transmitting) to the user 20* aneditable form of the hypothesis 60 including at least an editablesymbolic representation representing the relationship between the firstevent type and the second event type.

For example, in some implementations, the editable form of thehypothesis 60 may be presented, for example, on a display monitor ingraphical or pictorial form showing a first and a second iconrepresenting the first event type and the second event type. Therelationship (e.g., spatial or temporal/specific time relationship)between the first event type and the second event type may berepresented in the graphical representation by spacing between the firstand the second icon (e.g., the first and second icons being set againsta grid background), a line between the first and the second icon, anarrow between the first and the second icon, and so forth, that may beeditable. In this example, the symbolic representation representing therelationship between the first event type and the second event typewould be the spacing between the first and the second icon, the linebetween the first and the second icon, the arrow between the first andthe second icon, and so forth,

As further depicted in FIG. 4 c, in some implementations, operation 418may include an operation 419 for presenting to the user an editable formof the hypothesis including at least a deletable symbolic representationrepresenting the relationship between the first event type and thesecond event type as depicted in FIG. 4 c. For instance, the editablehypothesis presentation module 212* of the mobile device 30 or thecomputing device 10 presenting (e.g., audioally or visually indicatingor transmitting) to the user 20* an editable form of the hypothesis 60including at least a deletable symbolic representation representing therelationship between the first event type and the second event type. Forexample, a pictorial or textual form of the hypothesis 60 may bepresented, and at least the portion of the hypothesis 60 that indicatesthe relationship between the first event type and the second event typemay be deletable (e.g., erasable).

In the same or different implementations, operation 418 may include anoperation 420 for presenting to the user an editable form of thehypothesis including at least a modifiable symbolic representationrepresenting the relationship between the first event type and thesecond event type as depicted in FIG. 4 c. For instance, the editablehypothesis presentation module 212* of the mobile device 30 or thecomputing device 10 presenting (e.g., audioally or visually indicatingor transmitting) to the user 20* an editable form of the hypothesis 60including at least a modifiable symbolic representation representing therelationship between the first event type and the second event type. Forexample, suppose an editable form of the hypothesis 60 is presented intextual form that indicates that the user 20* “will become depressedafter overcast weather.” The phrase “after” in the message defines therelationship between the first event type (e.g., depressed) and thesecond event type (e.g., overcast weather) and may be modifiable (e.g.,non-deletion editable) to be switched from “after” to “during.”

In some implementations, operation 414 of FIG. 4 c for presenting aneditable form of the hypothesis may include an operation 421 forpresenting to the user an editable form of the hypothesis including aneditable symbolic representation representing a third event type asdepicted in FIG. 4 d. For instance, the editable hypothesis presentationmodule 212* of the mobile device 30 or the computing device 10presenting (e.g., audioally or visually indicating or transmitting) tothe user 20* an editable form of the hypothesis 60 including an editable(e.g., deletable and/or modifiable) symbolic representation (e.g., audioor visual representation) representing a third event type (e.g., asubjective user state, an objective occurrence, or a subjectiveobservation).

As further depicted in FIG. 4 d, operation 421 may further include, invarious implementations, an operation 422 for presenting to the user aneditable form of the hypothesis including a deletable symbolicrepresentation representing the third event type. For instance, theeditable hypothesis presentation module 212* of the mobile device 30 orthe computing device 10 presenting (e.g., audioally or visuallyindicating or transmitting) to the user 20* an editable form of thehypothesis 60 including a deletable symbolic representation representingthe third event type.

In the same or different implementations, operation 421 may include anoperation 423 for presenting to the user an editable form of thehypothesis including a modifiable symbolic representation representingthe third event type as depicted in FIG. 4 d. For instance, the editablehypothesis presentation module 212* of the mobile device 30 or thecomputing device 10 presenting (e.g., audioally or visually indicatingor transmitting) to the user 20* an editable form of the hypothesis 60 amodifiable symbolic representation representing the third event type.

In the same or different implementations, operation 421 may include anoperation 424 for presenting to the user an editable form of thehypothesis including another editable symbolic representationrepresenting a fourth event type as depicted in FIG. 4 d. For instance,the editable hypothesis presentation module 212* of the mobile device 30or the computing device 10 presenting (e.g., audioally or visuallyindicating or transmitting) to the user 20* an editable form of thehypothesis 60 including another editable symbolic representation (e.g.,audio or visual representation) representing a fourth event type.

In various implementations, operation 424 may further include anoperation 425 for presenting to the user an editable form of thehypothesis including a deletable symbolic representation representingthe fourth event type as depicted in FIG. 4 d. For instance, theeditable hypothesis presentation module 212* of the mobile device 30 orthe computing device 10 presenting (e.g., audioally or visuallyindicating or transmitting) to the user 20* an editable form of thehypothesis 60 including a deletable (e.g. erasable) symbolicrepresentation representing the fourth event type.

In the same or different implementations, operation 424 may include anoperation 426 for presenting to the user an editable form of thehypothesis including a modifiable symbolic representation representingthe fourth event type as depicted in FIG. 4 d. For instance, theeditable hypothesis presentation module 212* of the mobile device 30 orthe computing device 10 presenting (e.g., audioally or visuallyindicating or transmitting) to the user 20* an editable form of thehypothesis 60 including a modifiable symbolic representationrepresenting the fourth event type (e.g., a subjective user state, anobjective occurrence, or a subjective observation).

Referring back to the hypothesis presentation operation 302 of FIG. 3,in various implementations, the hypothesis presentation operation 302may provide for one or more options. For example, in someimplementations, the hypothesis presentation operation 302 may includean operation 427 for presenting to the user an option to delete thehypothesis as depicted in FIG. 4 e. For instance, the hypothesisdeletion option presentation module 214* of the mobile device 30 or thecomputing device 10 presenting to the user 20* an option to delete thehypothesis 60. Such an option may allow a user 20* to delete ahypothesis 60* that the user 20*, for example, feels is irrelevant orwish to ignore.

In the same or different implementations, the hypothesis presentationoperation 302 may include an operation 428 for presenting to the user anoption to deactivate or ignore the hypothesis as depicted in FIG. 4 e.For instance, the hypothesis deactivation option presentation module216* of the mobile device 30 or the computing device 10 presenting tothe user 20* an option to deactivate or ignore the hypothesis 60. Bydeactivating the hypothesis 60, the action execution module 108* of themobile device 30 or the computing device 10 may be prevented fromexecuting one or more actions based on the hypothesis 60 (e.g., or amodified version of the hypothesis 60).

Various types of relationships between various types of events may beindicated by the hypothesis 60 presented in the hypothesis presentationoperation 302 of FIG. 3. For example, in some implementations, thehypothesis presentation operation 302 may include an operation 429 forpresenting to the user a hypothesis identifying at least a time ortemporal relationship between the first event type and the second eventtype as depicted in FIG. 4 e. For instance, the hypothesis presentationmodule 102* of the mobile device 10 or the computing device 10presenting (e.g., audioally or visually indicating via a user interface122* or transmitting via wireless and/or wired network 40) to the user20* a hypothesis 60 identifying at least a time or temporal relationshipbetween the first event type and the second event type. For example,presenting to the user 20* a hypothesis 60 in textual form thatindicates that “whenever the user's friend borrows the car, the caralways appears to run worse afterwards.” In this example, “the user'sfriend borrows the car” represents the first event type, “the car alwaysappears to run worse” represents the second event type, and the“afterwards” represents the temporal relationship between the firstevent type and the second event type.

In some implementations, the hypothesis presentation operation 302 mayinclude an operation 430 for presenting to the user a hypothesisidentifying at least a spatial relationship between the first event typeand the second event type as depicted in FIG. 4 e. For instance, thehypothesis presentation module 102* of the mobile device 30 or thecomputing device 10 presenting (e.g., audioally or visually indicatingvia a user interface 122* or transmitting via wireless and/or wirednetwork 40) to the user 20* a hypothesis 60 identifying at least aspatial relationship between the first event type and the second eventtype. For example, presenting to the user 20* a hypothesis 60 in audioform that indicates that “whenever the spouse is working in anothercity, and the user is at home, the user is happy.” In this example, “thespouse is working” may represent the first event type, “the user ishappy” may represent the second event type, and the spouse working inanother city and the “user is at home” may represent the spatialrelationship between the first event type and the second event type.

In some implementations, the hypothesis presentation operation 302 mayinclude an operation 431 for presenting to the user a hypothesisidentifying at least a relationship between at least a first subjectiveuser state type and a second subjective user state type as depicted inFIG. 4 e. For instance, the hypothesis presentation module 102* of themobile device 30 or the computing device 10 presenting (e.g., audioallyor visually indicating via a user interface 122* or transmitting viawireless and/or wired network 40) to the user 20* a hypothesis 60identifying at least a relationship between at least a first subjectiveuser state type (e.g., anger) and a second subjective user state type(e.g., sore or stiff back).

In some implementations, the hypothesis presentation operation 302 mayinclude an operation 432 for presenting to the user a hypothesisidentifying at least a relationship between at least a subjective userstate type and a subjective observation type as depicted in FIG. 4 e.For instance, the hypothesis presentation module 102* of the mobiledevice 30 or the computing device 10 presenting (e.g., audioally orvisually indicating via a user interface 122* or transmitting viawireless and/or wired network 40) to the user 20* a hypothesis 60identifying at least a relationship between at least a subjective userstate type (e.g., tension) and a subjective observation type (e.g., bossappears to be angry).

In some implementations, the hypothesis presentation operation 302 mayinclude an operation 433 for presenting to the user a hypothesisidentifying at least a relationship between at least a subjective userstate type and an objective occurrence type as depicted in FIG. 4 e. Forinstance, the hypothesis presentation module 102* of the mobile device30 or the computing device 10 presenting (e.g., audioally or visuallyindicating via a user interface 122* or transmitting via wireless and/orwired network 40) to the user 20* a hypothesis 60 identifying at least arelationship between at least a subjective user state type (e.g.,fatigue) and an objective occurrence type (e.g., alcoholic consumption).

In some implementations, the hypothesis presentation operation 302 mayinclude an operation 434 for presenting to the user a hypothesisidentifying at least a relationship between at least a first subjectiveobservation type and a second subjective observation type as depicted inFIG. 4 e. For instance, the hypothesis presentation module 102* of themobile device 30 or the computing device 10 presenting (e.g., audioallyor visually indicating via a user interface 122* or transmitting viawireless and/or wired network 40) to the user 20* a hypothesis 60identifying at least a relationship between at least a first subjectiveobservation type (e.g., pet dog appears to be depressed) and a secondsubjective observation type (e.g., spouse appears to be depressed).

In some implementations, the hypothesis presentation operation 302 mayinclude an operation 435 for presenting to the user a hypothesisidentifying at least a relationship between at least a subjectiveobservation type and an objective occurrence type as depicted in FIG. 4e. For instance, the hypothesis presentation module 102* of the mobiledevice 30 or the computing device 10 presenting (e.g., audioally orvisually indicating via a user interface 122* or transmitting viawireless and/or wired network 40) to the user 20* a hypothesis 60identifying at least a relationship between at least a subjectiveobservation type (e.g., sore ankles) and an objective occurrence type(e.g., jogging).

In some implementations, the hypothesis presentation operation 302 mayinclude an operation 436 for presenting to the user a hypothesisidentifying at least a relationship between at least a first objectiveoccurrence type and a second objective occurrence type as depicted inFIG. 4 f. For instance, the hypothesis presentation module 102* of themobile device 30 or the computing device 10 presenting (e.g., audioallyor visually indicating via a user interface 122* or transmitting viawireless and/or wired network 40) a hypothesis 60 identifying at least arelationship between at least a first objective occurrence type (e.g.,elevated blood glucose level) and a second objective occurrence type(e.g., consumption of a particular type of food).

In various implementations, the hypothesis to be presented through thehypothesis presentation operation 302 of FIG. 3 may have been developedbased on data (e.g., events data that indicate previously reportedevents) provided by a user 20*. For example, in some implementations,the hypothesis presentation operation 302 may include an operation 437for presenting to the user a hypothesis that was developed based, atleast in part, on data provided by the user as depicted in FIG. 4 f. Forinstance, the hypothesis presentation module 102* of the mobile device30 or the computing device 10 presenting (e.g., audioally or visuallyindicating via a user interface 122* or transmitting via wireless and/orwired network 40) to the user 20* a hypothesis 60 that was developedbased, at least in part, on data provided by the user 20*. As a furtherillustration, a hypothesis 60* may be developed by, for example, thereported event reception module 110 of the computing device 10 receivingdata that indicates reported events reported by the user 20*. Based onthis data, and based at least in part on a pattern of reported events(e.g., spatial or temporal/time pattern of reported events) orreoccurring pattern of reported events identified by the hypothesisdevelopment module 112, the hypothesis development module 112 maydevelop a hypothesis 60.

The hypothesis to be presented through the hypothesis presentationoperation 302 of FIG. 3 may be directed to various subjects in variousalternative implementations. For example, in some implementations, thehypothesis presentation module 302 may include an operation 438 forpresenting to the user a hypothesis relating to the user as depicted inFIG. 4 f. For instance, the hypothesis presentation module 102* of themobile device 30 or the computing device 10 presenting (e.g., audioallyor visually indicating or transmitting) to the user 20* a hypothesis 60relating to the user 20*. For example, presenting to the user 20* ahypothesis 60 that indicates a relationship between a subjective userstate of the user 20* with consumption of a particular food item by theuser 20*.

In some implementations, the hypothesis presentation operation 302 mayinclude an operation 439 for presenting to the user a hypothesisrelating to a third party as depicted in FIG. 4 f. For instance, thehypothesis presentation module 102* of the mobile device 30 or thecomputing device 10 presenting (e.g., audioally or visually indicatingor transmitting) to the user 20* a hypothesis 60 relating to a thirdparty. For example, presenting to the user 20* a hypothesis 60 thatindicates a relationship between a subjective user state of a thirdparty (e.g., a pet such as a dog, livestock, a spouse, a friend, and soforth) with consumption of a particular food item by the third party.

In some implementations, the hypothesis presentation operation 302 mayinclude an operation 440 for presenting to the user a hypothesisrelating to a device as depicted in FIG. 4 f. For instance, thehypothesis presentation module 102* of the mobile device 30 or thecomputing device 10 presenting (e.g., audioally or visually indicatingor transmitting) to the user 20* a hypothesis 60 relating to a device.For example, presenting to the user 20* a hypothesis 60 that indicates arelationship between the use of a personal computer by an offspring andthe prevalence of computer viruses in the personal computer afterwards.

In some implementations, the hypothesis presentation operation 302 mayinclude an operation 441 for presenting to the user a hypothesisrelating to one or more environmental characteristics as depicted inFIG. 4 f. For instance, the hypothesis presentation module 102* of themobile device 30 or the computing device 10 presenting (e.g., audioallyor visually indicating or transmitting) to the user 20* a hypothesis 60relating to one or more environmental characteristics. For example,presenting to the user 20* a hypothesis 60 that indicates a relationshipbetween the local atmospheric pollution level (e.g., as sensed bypollution monitoring devices including those that measure gas and/orparticulate levels in the atmosphere) and when a particular factory isin operation.

In various embodiments, the hypothesis 60 to be presented through thehypothesis presentation operation 302 of FIG. 3 may be directed orrelated to three or more event types (e.g., types of events). Forexample, in some implementations, the hypothesis presentation operation302 may include an operation 442 for presenting to the user a hypothesisidentifying at least relationships between the first event type, thesecond event type, and a third event type as depicted in FIG. 4 f. Forinstance, the hypothesis presentation module 102* of the mobile device30 or the computing device 10 presenting (e.g., audioally or visuallyindicating or transmitting) to the user 20* a hypothesis 60 identifyingat least relationships between the first event type, the second eventtype, and a third event type. For example, presenting a hypothesis 60that identifies temporal relationships between eating ice cream,drinking coffee, and having a stomach ache.

In various implementations, operation 442 may further include anoperation 443 for presenting to the user a hypothesis identifying atleast relationships between the first event type, the second event type,the third event type, and a fourth event type as depicted in FIG. 4 f.For instance, the hypothesis presentation module 102* of the mobiledevice 30 or the computing device 10 presenting (e.g., audioally orvisually indicating or transmitting) to the user 20* a hypothesis 60identifying at least relationships between the first event type, thesecond event type, the third event type, and a fourth event type. Forexample, presenting a hypothesis 60 that identifies temporalrelationships between eating ice cream (e.g., first event type),drinking coffee (e.g., second event type), waking-up late (e.g., thirdevent type), and having a stomach ache (e.g., fourth event type). Notethat in this illustration, the user 20* after being presented with thehypothesis 60 may determine that the third event type, waking-up late,may not be relevant with respect to the hypothesis 60 (e.g., things thatmay be linked to a stomach ache). As a result, the user 20*, as will befurther described below, may delete the third event type from thehypothesis 60.

Referring back to the modification reception operation 304 of FIG. 3,the one or more modifications received through the modificationreception operation 304 may be received in a variety of different ways.For example, in various implementations, the modification receptionoperation 304 may include an operation 544 for receiving the one or moremodifications via a user interface as depicted in FIG. 5 a. Forinstance, the user interface reception module 218* of the mobile device30 or the computing device 10 (e.g., in embodiments in which thecomputing device 10 is a standalone device) receiving the one or moremodifications 61 via a user interface 122*(e.g., a microphone, a touchscreen, a keypad, a mouse, and so forth).

In some implementations, operation 544 may further include an operation545 for transmitting the one or more modifications to a server via atleast one of a wireless network and a wired network as depicted in FIG.5 a. For instance, the modification transmission module 219 of themobile device 30 transmitting (e.g., via a wireless and/or wired network40) the one or more modifications 61 to a server (e.g., computing device10 in embodiments in which the computing device 10 is a server) via atleast one of a wireless network and a wired network (e.g., via awireless and/or wired network 40).

In some implementations, the modification reception operation 304 mayinclude an operation 546 for receiving the one or more modificationsfrom at least one of a wireless network and a wired network as depictedin FIG. 5 a. For instance, the network reception module 220 of thecomputing device 10 (e.g., in embodiments where the computing device 10is a server) receiving the one or more modifications 61 (e.g., asprovided by the mobile device 30) from at least one of a wirelessnetwork and a wired network 40 (e.g., a wireless and/or wired network40).

The one or more modifications received through the modificationreception operation 304 of FIG. 3 may be received in a variety ofdifferent forms. For example, in some implementations, the modificationreception operation 304 may include an operation 547 for receiving theone or more modifications via one or more electronic entries as providedby the user as depicted in FIG. 5 a. For instance, the electronic entryreception module 222* of the mobile device 30 or the computing device 10receiving (e.g., receiving directly via a user interface 122* orindirectly via a wireless and/or wired network 40) the one or moremodifications 61 via one or more electronic entries as provided by theuser 20*.

In some implementations, operation 547 may include an operation 548 forreceiving the one or more modifications via one or more blog entries asprovided by the user as depicted in FIG. 5 a. For instance, the blogentry reception module 224* of the mobile device 30 or the computingdevice 10 receiving (e.g., receiving directly via a user interface 122*or indirectly via a wireless and/or wired network 40) the one or moremodifications 61 via one or more blog entries (e.g., microblog entries)as provided by the user 20*.

In some implementations, operation 547 may include an operation 549 forreceiving the one or more modifications via one or more status reportsas provided by the user as depicted in FIG. 5 a. For instance, thestatus report reception module 226* of the mobile device 30 or thecomputing device 10 receiving (e.g., receiving directly via a userinterface 122* or indirectly via a wireless and/or wired network 40) theone or more modifications 61 via one or more (social networking) statusreports as provided by the user 20*.

In some implementations, operation 547 may include an operation 550 forreceiving the one or more modifications via one or more electronicmessages as provided by the user as depicted in FIG. 5 a. For instance,the electronic message reception module 228* of the mobile device 30 orthe computing device 10 receiving (e.g., receiving directly via a userinterface 122* or indirectly via a wireless and/or wired network 40) theone or more modifications 61 via one or more electronic messages (e.g.,emails, text messages, IM messages, and so forth) as provided by theuser 20*.

In some implementations, operation 547 may include an operation 551 forreceiving the one or more modifications via one or more diary entries asprovided by the user as depicted in FIG. 5 a. For instance, the diaryentry reception module 230* of the mobile device 30 or the computingdevice 10 receiving (e.g., receiving directly via a user interface 122*or indirectly via a wireless and/or wired network 40) the one or moremodifications 61 via one or more diary entries as provided by the user20*.

Various types of modifications may be received through the modificationreception operation 304 of FIG. 3 in various alternativeimplementations. For example, in some implementations, the modificationreception operation 304 may include an operation 552 for receiving fromthe user a modification to delete a third event type from the hypothesisas depicted in FIG. 5 a. For instance, the modification reception module104* of the mobile device 30 or the computing device 10 receiving fromthe user 20* a modification 61 to delete a third event type from thehypothesis 60.

In certain implementations, operation 552 may further include anoperation 553 for receiving from the user a modification to delete atleast a fourth event type from the hypothesis as depicted in FIG. 5 a.For instance, the modification reception module 104* of the mobiledevice 30 or the computing device 10 receiving from the user 20* amodification 61 to delete at least a fourth event type from thehypothesis 60.

In various implementations, the modification reception operation 304 ofFIG. 3 may include an operation 554 for receiving from the user amodification to add to the hypothesis a third event type with respect tothe first event type and the second event type as depicted in FIG. 5 b.For instance, the modification reception module 104* of the mobiledevice 30 or the computing device 10 receiving from the user 20* amodification 61 to add to the hypothesis 60 a third event type withrespect to the first event type and the second event type. In otherwords, a modification to add to the hypothesis 60 a third event type andits spatial or time occurrence relative to the occurrences of the firstevent type and the second event type as indicated by the hypothesis 60.

In some implementations, operation 554 may further include an operation555 for receiving from the user a modification to add to the hypothesisat least a fourth event type with respect to the first event type andthe second event type, and with respect to the third event type to beadded to the hypothesis as depicted in FIG. 5 b. For instance, themodification reception module 104* of the mobile device 30 or thecomputing device 10 receiving from the user 20* a modification 61 to addto the hypothesis 60 at least a fourth event type with respect to thefirst event type and the second event type, and with respect to thethird event type to be added to the hypothesis 60.

In various implementations, the modification reception operation 304 ofFIG. 3 may include an operation 556 for receiving from the user amodification to revise the first event type of the hypothesis asdepicted in FIG. 5 b. For instance, the modification reception module104* of the mobile device 30 or the computing device 10 receiving fromthe user 20* a modification 61 to revise the first event type of thehypothesis 60*(e.g., revising a subjective user state such as “anger” toanother subjective user state such as “disappointment”).

In some implementations, operation 556 may further include an operation557 for receiving from the user a modification to revise the secondevent type of the hypothesis as depicted in FIG. 5 b. For instance, themodification reception module 104* of the mobile device 30 or thecomputing device 10 receiving from the user 20* a modification to revisethe second event type of the hypothesis 60 (e.g., an objectiveoccurrence such as a co-worker not coming to work to another objectiveoccurrence such as a co-worker coming to work late).

In some implementations, the modification reception operation 304 ofFIG. 3 may include an operation 558 for receiving from the user amodification to revise the relationship between the first event type andthe second event type as depicted in FIG. 5 b. For instance, themodification reception module 104* of the mobile device 30 or thecomputing device 10 receiving from the user 20* a modification 61 torevise the relationship between the first event type and the secondevent type (e.g., changing the temporal relationship between the firstevent type and the second event type as indicated by the hypothesis 60).

In some implementations, the modification reception operation 304 mayinclude an operation 559 for receiving from the user a modification tomodify at least one of the first event type and the second event typeincluding at least one type of subjective user state as depicted in FIG.5 b. For instance, the modification reception module 104* of the mobiledevice 30 or the computing device 10 receiving from the user 20* amodification 61 to modify at least one of the first event type and thesecond event type including at least one type of subjective user state(e.g., a subjective user state, a subjective physical state, or asubjective overall state).

In some implementations, the modification reception operation 304 mayinclude an operation 560 for receiving from the user a modification tomodify at least one of the first event type and the second event typeincluding at least one type of subjective observation as depicted inFIG. 5 b. For instance, the modification reception module 104* of themobile device 30 or the computing device 10 receiving from the user 20*a modification 61 to modify at least one of the first event type and thesecond event type including at least one type of subjective observation(e.g., perceived subjective user state of a third party, a subjectiveobservation or opinion regarding an external activity, a user'sactivity, or a third party's activity, a subjective observation oropinion regarding performance or characteristic of a device, and soforth).

In some implementations, the modification reception operation 304 mayinclude an operation 561 for receiving from the user a modification tomodify at least one of the first event type and the second event typeincluding at least one type of objective occurrence as depicted in FIG.5 b. For instance, the modification reception module 104* of the mobiledevice 30 or the computing device 10 receiving from the user 20* amodification 61 to modify at least one of the first event type and thesecond event type including at least one type of objective occurrence(e.g., consumption of a food item, medicine, or nutraceutical by theuser 20* or by a third party 50, an activity executed by the user 20* orby a third party 50, an external activity, an objectively measurablephysical characteristic of the user 20* or of a third party 50, and soforth).

In some implementations, the modification reception operation 304 mayinclude an operation 562 for modifying the hypothesis based on the oneor more modifications to generate the modified hypothesis as depicted inFIG. 5 b. For instance, the hypothesis modification module 106 of thecomputing device 10 modifying the hypothesis 60 based on the one or moremodifications 61 (e.g., as received by the modification reception module104 of the computing device 10) to generate the modified hypothesis 80.

Referring back to the action execution operation 306 of FIG. 3, varioustypes of actions may be executed in action execution operation 306 invarious alternative implementations. For example, in someimplementations, the action execution operation 306 may include anoperation 663 for presenting one or more advisories relating to themodified hypothesis as depicted in FIG. 6 a. For instance, the advisorypresentation module 232* of the mobile device 30 or the computing device10 presenting (e.g., indicating via a user interface 122* ortransmitting via a wireless and/or wired network 40) one or moreadvisories 90 relating to the modified hypothesis 80.

Various types of advisories may be presented through operation 663. Forexample, in some implementations, operation 663 may include an operation664 for indicating the one or more advisories relating to the modifiedhypothesis via user interface as depicted in FIG. 6 a. For instance, theuser interface indication module 234* of the mobile device 30 or thecomputing device 10 indicating (e.g., audioally indicating and/orvisually displaying) the one or more advisories 90 relating to themodified hypothesis 80 via user interface 122*(e.g., an audio systemincluding one or more speakers and/or a display system including adisplay monitor or touch screen).

In some selective implementations, operation 664 may include anoperation 665 for receiving the one or more advisories from a serverprior to said indicating as depicted in FIG. 6 a. For instance, theadvisory reception module 235 of the mobile device 30 receiving the oneor more advisories 90 from a server (e.g., the computing device 10 inembodiments where the computing device 10 is a network server) prior tosaid indicating of the one or more advisories 90.

In the same or different implementations, operation 663 may include anoperation 666 for transmitting the one or more advisories related to themodified hypothesis via at least one of a wireless network and a wirednetwork as depicted in FIG. 6 a. For instance, the network transmissionmodule 236* of the mobile device 30 or the computing device 10transmitting the one or more advisories 90 related to the modifiedhypothesis 80 via at least one of a wireless network and a wired network40. Note that, in addition to or instead of presenting the one or moreadvisories 90 to the user 20*, the one or more advisories 90 may betransmitted by the mobile device 30 or the computing device 10 to, forexample, one or more third parties 50.

In various implementations, operation 666 may further include anoperation 667 for transmitting the one or more advisories related to themodified hypothesis to the user as depicted in FIG. 6 a. For instance,the network transmission module 236 of the computing device 10 (e.g., inembodiments in which the computing device 10 is a server) transmittingthe one or more advisories 90 related to the modified hypothesis 80 tothe user 20 a.

In some implementations, operation 666 may include an operation 668 fortransmitting the one or more advisories related to the modifiedhypothesis to one or more third parties as depicted in FIG. 6 a. Forinstance, the network transmission module 236* of the mobile device 30or the computing device 10 transmitting the one or more advisories 90related to the modified hypothesis 80 to one or more third parties 50.

In various implementations, the modified hypothesis 80 may be presentedthrough operation 663. For example, in some implementations, operation663 may include an operation 669 for presenting at least one form of themodified hypothesis as depicted in FIG. 6 a. For instance, the modifiedhypothesis presentation module 238* of the mobile device 30 or thecomputing device 10 presenting at least one form (e.g., audio formand/or visual form such as textual, graphical, or pictorial form) of themodified hypothesis 80.

Operation 669, in turn, may include an operation 670 for presenting anindication of a relationship between at least two event types asindicated by the modified hypothesis as depicted in FIG. 6 a. Forinstance, the modified hypothesis presentation module 238* of the mobiledevice 30 or the computing device 10 presenting (e.g., indicating via auser interface 122 or transmitting via wireless and/or wired network 40)an indication of a relationship (e.g., spatial or temporal/specific timerelationship) between at least two event types as indicated by themodified hypothesis 80.

In some implementations, operation 670 may include an operation 671 forpresenting an indication of a temporal or specific time relationshipbetween the at least two event types as indicated by the modifiedhypothesis as depicted in FIG. 6 a. For instance, the modifiedhypothesis presentation module 238* of the mobile device 30 or thecomputing device 10 presenting an indication of a temporal or specifictime relationship between the at least two event types as indicated bythe modified hypothesis 80.

In the same or alternative implementations, operation 670 may include anoperation 672 for presenting an indication of a spatial relationshipbetween the at least two event types as indicated by the modifiedhypothesis as depicted in FIG. 6 a. For instance, the modifiedhypothesis presentation module 238* of the mobile device 30 or thecomputing device 10 presenting an indication of a spatial relationshipbetween the at least two event types as indicated by the modifiedhypothesis 80.

In the same or different implementations, operation 670 may include anoperation 673 for presenting an indication of a relationship between atleast a first type of subjective user state and a second type ofsubjective user state as indicated by the modified hypothesis asdepicted in FIG. 6 a. For instance, the modified hypothesis presentationmodule 238* of the mobile device 30 or the computing device 10presenting an indication of a relationship between at least a first typeof subjective user state (e.g., jealousy) and a second type ofsubjective user state (e.g., depression) as indicated by the modifiedhypothesis 80.

In the same or different implementations, operation 670 may include anoperation 674 for presenting an indication of a relationship between atleast a type of subjective user state and a type of objective occurrenceas indicated by the modified hypothesis as depicted in FIG. 6 b. Forinstance, the modified hypothesis presentation module 238* of the mobiledevice 30 or the computing device 10 presenting an indication of arelationship between at least a type of subjective user state (e.g.,subjective overall state such as “great”) and a type of objectiveoccurrence (e.g., fishing) as indicated by the modified hypothesis 80.

In the same or different implementations, operation 670 may include anoperation 675 for presenting an indication of a relationship between atleast a type of subjective user state and a type of subjectiveobservation as indicated by the modified hypothesis as depicted in FIG.6 b. For instance, the modified hypothesis presentation module 238* ofthe mobile device 30 or the computing device 10 presenting an indicationof a relationship between at least a type of subjective user state(e.g., fear) and a type of subjective observation (e.g., spouseperceived to be angry) as indicated by the modified hypothesis 80.

In the same or different implementations, operation 670 may include anoperation 676 for presenting an indication of a relationship between atleast a first type of objective occurrence and a second type ofobjective occurrence as indicated by the modified hypothesis as depictedin FIG. 6 b. For instance, the modified hypothesis presentation module238* of the mobile device 30 or the computing device 10 presenting anindication of a relationship between at least a first type of objectiveoccurrence (e.g., off-spring parents' car) and a second type ofobjective occurrence (e.g., low fuel level in the car) as indicated bythe modified hypothesis 80.

In the same or different implementations, operation 670 may include anoperation 677 for presenting an indication of a relationship between atleast a type of objective occurrence and a type of subjectiveobservation as indicated by the modified hypothesis as depicted in FIG.6 b. For instance, the modified hypothesis presentation module 238* ofthe mobile device 30 or the computing device 10 presenting an indicationof a relationship between at least a type of objective occurrence (e.g.,staying home on wedding anniversary) and a type of subjectiveobservation (e.g., spouse appears to be in bad mood) as indicated by themodified hypothesis 80.

In the same or different implementations, operation 670 may include anoperation 678 for presenting an indication of a relationship between atleast a first type of subjective observation and a second type ofsubjective observation as indicated by the modified hypothesis asdepicted in FIG. 6 b. For instance, the modified hypothesis presentationmodule 238* of the mobile device 30 or the computing device 10presenting an indication of a relationship between at least a first typeof subjective observation (e.g., “bad weather”) and a second type ofsubjective observation (e.g., spouse appears to be in bad mood) asindicated by the modified hypothesis 80.

In various implementations, operation 663 of FIG. 6 a for presenting oneor more advisories 90 may include an operation 679 for presenting anadvisory relating to a predication of one or more future events based,at least in part, on the modified hypothesis as depicted in FIG. 6 c.For instance, the prediction presentation module 240* of the mobiledevice 30 or the computing device 10 presenting (e.g., indicating via auser interface 122* or transmitting via a wireless and/or wired network40) an advisory 90 relating to a predication of one or more futureevents (e.g., “you will have a headache tomorrow morning because youdrank last night”) based, at least in part, on the modified hypothesis80.

In various implementations, operation 663 may include an operation 680for presenting a recommendation for a future course of action based, atleast in part, on the modified hypothesis as depicted in FIG. 6 c. Forinstance, the recommendation presentation module 242* of the mobiledevice 30 or the computing device 10 presenting (e.g., indicating via auser interface 122* or transmitting via a wireless and/or wired network40) a recommendation for a future course of action (e.g., “you shouldbring aspirin to work tomorrow”) based, at least in part, on themodified hypothesis 80.

In some implementations, operation 680 may further include an operation681 for presenting a justification for the recommendation as depicted inFIG. 6 c. For instance, the justification presentation module 244* ofthe mobile device 30 or the computing device 10 presenting ajustification for the recommendation (e.g., “you should bring aspirin towork tomorrow because you drank 12 mugs of beer tonight”).

In some implementations, operation 663 may include an operation 682 forpresenting an indication of one or more past events based, at least inpart, on the modified hypothesis as depicted in FIG. 6 c. For instance,the past event presentation module 246* of the mobile device 30 or thecomputing device 10 presenting (e.g., indicating via a user interface122* or transmitting via a wireless and/or wired network 40) anindication of one or more past events based, at least in part, on themodified hypothesis 80 (e.g., “the last time you drank 12 mugs of beer,you had a hangover the next morning”).

Referring back to the action execution operation 306 of FIG. 3, theaction execution operation 306, in various alternative implementations,may include prompting 91* one or more devices to execute one or moreoperations. For example, in some implementations, the action executionoperation 306 may include an operation 683 for prompting one or moredevices to execute one or more operations based, at least in part, onthe modified hypothesis as depicted in FIG. 6 d. For instance, thedevice prompting module 248* of the mobile device 30 or the computingdevice 10 prompting 91* one or more devices (e.g., network and/or localdevices 55 and/or sensing devices 35*) to execute one or more operationsbased, at least in part, on the modified hypothesis 80.

Various techniques may be employed in order to prompt one or moredevices to execute one or more operations in various alternativeimplementations. For example, in some implementations, operation 683 mayinclude an operation 684 for instructing the one or more devices toexecute the one or more operations as depicted in FIG. 6 d. Forinstance, the device instruction module 250* of the mobile device 30 orthe computing device 10 instructing the one or more devices (e.g.,directly instructing a local device or indirectly instructing a remotenetwork device via wireless and/or wired network 40) to execute the oneor more operations. As an illustration, instructing a home appliance ora sensing device 35* to execute one or more operations in accordancewith instructions provided by the device instruction module 250*.

In some implementations, operation 683 may include an operation 685 foractivating the one or more devices to execute the one or more operationsas depicted in FIG. 6 d. For instance, the device activation module 252*of the mobile device 30 or the computing device 10 activating (e.g.,directly activating a local device or indirectly activating a networkdevice via wireless and/or wired network 40) the one or more devices(e.g., a home environmental device such as an air conditioner or an airpurifier) to execute the one or more operations.

In some implementations, operation 683 may include an operation 686 forconfiguring the one or more devices to execute the one or moreoperations as depicted in FIG. 6 d. For instance, the deviceconfiguration module 254* of the mobile device 30 or the computingdevice 10 configuring (e.g., directly configuring a local device orindirectly configuring a network device via wireless and/or wirednetwork 40) the one or more devices (e.g., a personal device such as themobile device 30 or a standalone computing device 10) to execute the oneor more operations.

Various types of devices may be prompted through operation 683 invarious alternative implementations. For example, in someimplementations, operation 683 may include an operation 687 forprompting one or more environmental devices to execute the one or moreoperations as depicted in FIG. 6 d. For instance, the device promptingmodule 248* of the mobile device 30 or the computing device 10 prompting91* one or more environmental devices (e.g., air conditioner,humidifier, air purifier, and so forth) to execute the one or moreoperations.

In some implementations, operation 683 may include an operation 688 forprompting one or more household devices to execute the one or moreoperations as depicted in FIG. 6 d. For instance, the device promptingmodule 250* of the mobile device 30 or the computing device 10 promptingone or more household devices (e.g., a television, hot water heater,lawn sprinkler system, and so forth) to execute the one or moreoperations.

In some implementations, operation 683 may include an operation 689 forprompting one or more sensing devices to execute the one or moreoperations as depicted in FIG. 6 d. For instance, the device promptingmodule 248* of the mobile device 30 or the computing device 10 prompting91* one or more sensing devices 35* to execute (e.g., physical orphysiological sensing devices, environmental sensing devices, GPSs,pedometers, accelerometers, and so forth) the one or more operations.

In some implementations, operation 683 may include an operation 690 forprompting one or more network devices to execute the one or moreoperations as depicted in FIG. 6 d. For instance, the device promptingmodule 248* of the mobile device 30 or the computing device 10 promptingone or more network devices (e.g., devices that can interface with awireless and/or wired network 40) to execute the one or more operations.

Referring back to the action execution operation 306 of FIG. 3, invarious implementations, the one or more actions to be executed throughaction execution operation 306 may be executed in response to receivinga request or instructions from network device such as a server. Forexample, in some implementations, the action execution operation 306 mayinclude an operation 691 for executing the one or more actions based, atleast in part, on a request or instructions received from a server asdepicted in FIG. 6 d. For instance, the action execution module 108′ ofthe mobile device 30 executing the one or more actions based, at leastin part, on a request or instructions received (e.g., as received by therequest/instruction reception module 237 of the mobile device 30) from aserver (e.g., computing device 10 in embodiments where the computingdevice 10 is a network server).

The one or more actions to be executed in the action execution operation306 of FIG. 3 may be in response to a reported event in addition tobeing based at least in part to the modified hypothesis 80. For example,in various implementations, the action execution operation 306 mayinclude an operation 692 for executing the one or more actions based onthe modified hypothesis and in response to a reported event as depictedin FIG. 6 e. For instance, the action execution module 108* of themobile device 30 or the computing device 10 executing the one or moreactions based on the modified hypothesis 80 and in response to areported event (e.g., in response to the reported event reception module110* of the mobile device 30 or the computing device 10 receiving dataindicating a reported event).

In some implementations, operation 692 may further include an operation693 for executing the one or more actions based on the modifiedhypothesis and in response to a reported event that at leastsubstantially matches with one of at least two event types identified bythe modified hypothesis as depicted in FIG. 6 e. For instance, theaction execution module 108* of the mobile device 30 or the computingdevice 10 executing the one or more actions based on the modifiedhypothesis 80 and in response to a reported event that substantiallymatches with one of at least two event types identified by the modifiedhypothesis 80. To illustrate, suppose the modified hypothesis 80indicates a relationship between eating a particular Mexican dish at aparticular restaurant (e.g., an event type) with a stomach ache (e.g.,another event type). Under this scenario, the action execution module108* may execute an action (e.g., indicate a warning about a pendingstomach ache) if it is reported that a similar Mexican dish was consumedat the same restaurant (e.g., reported event).

Operation 693, in turn, may further include an operation 694 forexecuting the one or more actions based on the modified hypothesis andin response to a reported event that matches with one of the at leasttwo event types identified by the modified hypothesis as depicted inFIG. 6 e. For instance, the action execution module 108* of the mobiledevice 30 or the computing device 10 executing the one or more actionsbased on the modified hypothesis 80 and in response to a reported event(e.g., in response to the reported event reception module 110* of themobile device 30 or the computing device 10 receiving data indicating areported event) that matches with one of the at least two event typesidentified by the modified hypothesis 80. To illustrate, suppose themodified hypothesis 80 indicates a relationship between exercising on atreadmill (e.g., an event type) and feeling hot (e.g., another eventtype). Under this scenario, the action execution module 108* may executean action (e.g., configuring an air conditioner to operate at fullpower) if it is reported that the treadmill was used for exercising(e.g., reported event).

Those having skill in the art will recognize that the state of the arthas progressed to the point where there is little distinction leftbetween hardware and software implementations of aspects of systems; theuse of hardware or software is generally (but not always, in that incertain contexts the choice between hardware and software can becomesignificant) a design choice representing cost vs. efficiency tradeoffs.Those having skill in the art will appreciate that there are variousvehicles by which processes and/or systems and/or other technologiesdescribed herein can be effected (e.g., hardware, software, and/orfirmware), and that the preferred vehicle will vary with the context inwhich the processes and/or systems and/or other technologies aredeployed. For example, if an implementer determines that speed andaccuracy are paramount, the implementer may opt for a mainly hardwareand/or firmware vehicle; alternatively, if flexibility is paramount, theimplementer may opt for a mainly software implementation; or, yet againalternatively, the implementer may opt for some combination of hardware,software, and/or firmware. Hence, there are several possible vehicles bywhich the processes and/or devices and/or other technologies describedherein may be effected, none of which is inherently superior to theother in that any vehicle to be utilized is a choice dependent upon thecontext in which the vehicle will be deployed and the specific concerns(e.g., speed, flexibility, or predictability) of the implementer, any ofwhich may vary. Those skilled in the art will recognize that opticalaspects of implementations will typically employ optically-orientedhardware, software, and or firmware.

The foregoing detailed description has set forth various embodiments ofthe devices and/or processes via the use of block diagrams, flowcharts,and/or examples. Insofar as such block diagrams, flowcharts, and/orexamples contain one or more functions and/or operations, it will beunderstood by those within the art that each function and/or operationwithin such block diagrams, flowcharts, or examples can be implemented,individually and/or collectively, by a wide range of hardware, software,firmware, or virtually any combination thereof. In one embodiment,several portions of the subject matter described herein may beimplemented via Application Specific Integrated Circuits (ASICs), FieldProgrammable Gate Arrays (FPGAs), digital signal processors (DSPs), orother integrated formats. However, those skilled in the art willrecognize that some aspects of the embodiments disclosed herein, inwhole or in part, can be equivalently implemented in integratedcircuits, as one or more computer programs running on one or morecomputers (e.g., as one or more programs running on one or more computersystems), as one or more programs running on one or more processors(e.g., as one or more programs running on one or more microprocessors),as firmware, or as virtually any combination thereof, and that designingthe circuitry and/or writing the code for the software and or firmwarewould be well within the skill of one of skill in the art in light ofthis disclosure. In addition, those skilled in the art will appreciatethat the mechanisms of the subject matter described herein are capableof being distributed as a program product in a variety of forms, andthat an illustrative embodiment of the subject matter described hereinapplies regardless of the particular type of signal bearing medium usedto actually carry out the distribution. Examples of a signal bearingmedium include, but are not limited to, the following: a recordable typemedium such as a floppy disk, a hard disk drive, a Compact Disc (CD), aDigital Video Disk (DVD), a digital tape, a computer memory, etc.; and atransmission type medium such as a digital and/or an analogcommunication medium (e.g., a fiber optic cable, a waveguide, a wiredcommunications link, a wireless communication link, etc.).

In a general sense, those skilled in the art will recognize that thevarious aspects described herein which can be implemented, individuallyand/or collectively, by a wide range of hardware, software, firmware, orany combination thereof can be viewed as being composed of various typesof “electrical circuitry.” Consequently, as used herein “electricalcircuitry” includes, but is not limited to, electrical circuitry havingat least one discrete electrical circuit, electrical circuitry having atleast one integrated circuit, electrical circuitry having at least oneapplication specific integrated circuit, electrical circuitry forming ageneral purpose computing device configured by a computer program (e.g.,a general purpose computer configured by a computer program which atleast partially carries out processes and/or devices described herein,or a microprocessor configured by a computer program which at leastpartially carries out processes and/or devices described herein),electrical circuitry forming a memory device (e.g., forms of randomaccess memory), and/or electrical circuitry forming a communicationsdevice (e.g., a modem, communications switch, or optical-electricalequipment). Those having skill in the art will recognize that thesubject matter described herein may be implemented in an analog ordigital fashion or some combination thereof.

Those having skill in the art will recognize that it is common withinthe art to describe devices and/or processes in the fashion set forthherein, and thereafter use engineering practices to integrate suchdescribed devices and/or processes into data processing systems. Thatis, at least a portion of the devices and/or processes described hereincan be integrated into a data processing system via a reasonable amountof experimentation. Those having skill in the art will recognize that atypical data processing system generally includes one or more of asystem unit housing, a video display device, a memory such as volatileand non-volatile memory, processors such as microprocessors and digitalsignal processors, computational entities such as operating systems,drivers, graphical user interfaces, and applications programs, one ormore interaction devices, such as a touch pad or screen, and/or controlsystems including feedback loops and control motors (e.g., feedback forsensing position and/or velocity; control motors for moving and/oradjusting components and/or quantities). A typical data processingsystem may be implemented utilizing any suitable commercially availablecomponents, such as those typically found in datacomputing/communication and/or network computing/communication systems.

The herein described subject matter sometimes illustrates differentcomponents contained within, or connected with, different othercomponents. It is to be understood that such depicted architectures aremerely exemplary, and that in fact many other architectures can beimplemented which achieve the same functionality. In a conceptual sense,any arrangement of components to achieve the same functionality iseffectively “associated” such that the desired functionality isachieved. Hence, any two components herein combined to achieve aparticular functionality can be seen as “associated with” each othersuch that the desired functionality is achieved, irrespective ofarchitectures or intermedial components. Likewise, any two components soassociated can also be viewed as being “operably connected”, or“operably coupled”, to each other to achieve the desired functionality,and any two components capable of being so associated can also be viewedas being “operably couplable”, to each other to achieve the desiredfunctionality. Specific examples of operably couplable include but arenot limited to physically mateable and/or physically interactingcomponents and/or wirelessly interactable and/or wirelessly interactingcomponents and/or logically interacting and/or logically interactablecomponents.

While particular aspects of the present subject matter described hereinhave been shown and described, it will be apparent to those skilled inthe art that, based upon the teachings herein, changes and modificationsmay be made without departing from the subject matter described hereinand its broader aspects and, therefore, the appended claims are toencompass within their scope all such changes and modifications as arewithin the true spirit and scope of the subject matter described herein.Furthermore, it is to be understood that the invention is defined by theappended claims.

It will be understood by those within the art that, in general, termsused herein, and especially in the appended claims (e.g., bodies of theappended claims) are generally intended as “open” terms (e.g., the term“including” should be interpreted as “including but not limited to,” theterm “having” should be interpreted as “having at least,” the term“includes” should be interpreted as “includes but is not limited to,”etc.). It will be further understood by those within the art that if aspecific number of an introduced claim recitation is intended, such anintent will be explicitly recited in the claim, and in the absence ofsuch recitation no such intent is present. For example, as an aid tounderstanding, the following appended claims may contain usage of theintroductory phrases “at least one” and “one or more” to introduce claimrecitations. However, the use of such phrases should not be construed toimply that the introduction of a claim recitation by the indefinitearticles “a” or “an” limits any particular claim containing suchintroduced claim recitation to inventions containing only one suchrecitation, even when the same claim includes the introductory phrases“one or more” or “at least one” and indefinite articles such as “a” or“an” (e.g., “a” and/or “an” should typically be interpreted to mean “atleast one” or “one or more”); the same holds true for the use ofdefinite articles used to introduce claim recitations.

In addition, even if a specific number of an introduced claim recitationis explicitly recited, those skilled in the art will recognize that suchrecitation should typically be interpreted to mean at least the recitednumber (e.g., the bare recitation of “two recitations,” without othermodifiers, typically means at least two recitations, or two or morerecitations). Furthermore, in those instances where a conventionanalogous to “at least one of A, B, and C, etc.” is used, in generalsuch a construction is intended in the sense one having skill in the artwould understand the convention (e.g., “a system having at least one ofA, B, and C” would include but not be limited to systems that have Aalone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.).

In those instances where a convention analogous to “at least one of A,B, or C, etc.” is used, in general such a construction is intended inthe sense one having skill in the art would understand the convention(e.g., “a system having at least one of A, B, or C” would include butnot be limited to systems that have A alone, B alone, C alone, A and Btogether, A and C together, B and C together, and/or A, B, and Ctogether, etc.). It will be further understood by those within the artthat virtually any disjunctive word and/or phrase presenting two or morealternative terms, whether in the description, claims, or drawings,should be understood to contemplate the possibilities of including oneof the terms, either of the terms, or both terms. For example, thephrase “A or B” will be understood to include the possibilities of “A”or “B” or “A and B.”

1.-94. (canceled)
 95. A computationally-implemented system, comprising:means for presenting to a user a hypothesis identifying at least arelationship between a first event type and a second event type; meansfor receiving from the user one or more modifications to modify thehypothesis; and means for executing one or more actions based, at leastin part, on a modified hypothesis resulting, at least in part, from thereception of the one or more modifications. 96.-107. (canceled)
 108. Thecomputationally-implemented system of claim 95, wherein said means forpresenting to a user a hypothesis identifying at least a relationshipbetween a first event type and a second event type comprises: means forpresenting to the user an editable form of the hypothesis.
 109. Thecomputationally-implemented system of claim 108, wherein said means forpresenting to the user an editable form of the hypothesis comprises:means for presenting to the user an editable form of the hypothesisincluding at least a first editable symbolic representation representingthe first event type and a second editable symbolic representationrepresenting the second event type. 110.-121. (canceled)
 122. Thecomputationally-implemented system of claim 95, wherein said means forpresenting to a user a hypothesis identifying at least a relationshipbetween a first event type and a second event type comprises: means forpresenting to the user an option to deactivate or ignore the hypothesis.123. The computationally-implemented system of claim 95, wherein saidmeans for presenting to a user a hypothesis identifying at least arelationship between a first event type and a second event typecomprises: means for presenting to the user a hypothesis identifying atleast a time or temporal relationship between the first event type andthe second event type.
 124. (canceled)
 125. Thecomputationally-implemented system of claim 95, wherein said means forpresenting to a user a hypothesis identifying at least a relationshipbetween a first event type and a second event type comprises: means forpresenting to the user a hypothesis identifying at least a relationshipbetween at least a first subjective user state type and a secondsubjective user state type.
 126. The computationally-implemented systemof claim 95, wherein said means for presenting to a user a hypothesisidentifying at least a relationship between a first event type and asecond event type comprises: means for presenting to the user ahypothesis identifying at least a relationship between at least asubjective user state type and a subjective observation type.
 127. Thecomputationally-implemented system of claim 95, wherein said means forpresenting to a user a hypothesis identifying at least a relationshipbetween a first event type and a second event type comprises: means forpresenting to the user a hypothesis identifying at least a relationshipbetween at least a subjective user state type and an objectiveoccurrence type.
 128. The computationally-implemented system of claim95, wherein said means for presenting to a user a hypothesis identifyingat least a relationship between a first event type and a second eventtype comprises: means for presenting to the user a hypothesisidentifying at least a relationship between at least a first subjectiveobservation type and a second subjective observation type.
 129. Thecomputationally-implemented system of claim 95, wherein said means forpresenting to a user a hypothesis identifying at least a relationshipbetween a first event type and a second event type comprises: means forpresenting to the user a hypothesis identifying at least a relationshipbetween at least a subjective observation type and an objectiveoccurrence type.
 130. (canceled)
 131. The computationally-implementedsystem of claim 95, wherein said means for presenting to a user ahypothesis identifying at least a relationship between a first eventtype and a second event type comprises: means for presenting to the usera hypothesis that was developed based, at least in part, on dataprovided by the user.
 132. The computationally-implemented system ofclaim 95, wherein said means for presenting to a user a hypothesisidentifying at least a relationship between a first event type and asecond event type comprises: means for presenting to the user ahypothesis relating to the user.
 133. The computationally-implementedsystem of claim 95, wherein said means for presenting to a user ahypothesis identifying at least a relationship between a first eventtype and a second event type comprises: means for presenting to the usera hypothesis relating to a third party.
 134. Thecomputationally-implemented system of claim 95, wherein said means forpresenting to a user a hypothesis identifying at least a relationshipbetween a first event type and a second event type comprises: means forpresenting to the user a hypothesis relating to a device.
 135. Thecomputationally-implemented system of claim 95, wherein said means forpresenting to a user a hypothesis identifying at least a relationshipbetween a first event type and a second event type comprises: means forpresenting to the user a hypothesis relating to one or moreenvironmental characteristics. 136.-140. (canceled)
 141. Thecomputationally-implemented system of claim 95, wherein said means forreceiving from the user one or more modifications to modify thehypothesis comprises: means for receiving the one or more modificationsvia one or more electronic entries as provided by the user.
 142. Thecomputationally-implemented system of claim 141, wherein said means forreceiving the one or more modifications via one or more electronicentries as provided by the user comprises: means for receiving the oneor more modifications via one or more blog entries as provided by theuser.
 143. The computationally-implemented system of claim 141, whereinsaid means for receiving the one or more modifications via one or moreelectronic entries as provided by the user comprises: means forreceiving the one or more modifications via one or more status reportsas provided by the user.
 144. (canceled)
 145. Thecomputationally-implemented system of claim 141, wherein said means forreceiving the one or more modifications via one or more electronicentries as provided by the user comprises: means for receiving the oneor more modifications via one or more diary entries as provided by theuser. 146.-149. (canceled)
 150. The computationally-implemented systemof claim 95, wherein said means for receiving from the user one or moremodifications to modify the hypothesis comprises: means for receivingfrom the user a modification to revise the first event type of thehypothesis.
 151. The computationally-implemented system of claim 150,wherein said means for receiving from the user a modification to revisethe first event type of the hypothesis comprises: means for receivingfrom the user a modification to revise the second event type of thehypothesis.
 152. The computationally-implemented system of claim 95,wherein said means for receiving from the user one or more modificationsto modify the hypothesis comprises: means for receiving from the user amodification to revise the relationship between the first event type andthe second event type.
 153. The computationally-implemented system ofclaim 95, wherein said means for receiving from the user one or moremodifications to modify the hypothesis comprises: means for receivingfrom the user a modification to modify at least one of the first eventtype and the second event type including at least one type of subjectiveuser state.
 154. The computationally-implemented system of claim 95,wherein said means for receiving from the user one or more modificationsto modify the hypothesis comprises: means for receiving from the user amodification to modify at least one of the first event type and thesecond event type including at least one type of subjective observation.155. The computationally-implemented system of claim 95, wherein saidmeans for receiving from the user one or more modifications to modifythe hypothesis comprises: means for receiving from the user amodification to modify at least one of the first event type and thesecond event type including at least one type of objective occurrence.156. The computationally-implemented system of claim 95, furthercomprising: means for modifying the hypothesis based on the one or moremodifications to generate the modified hypothesis.
 157. Thecomputationally-implemented system of claim 95, wherein said means forsaid executing one or more actions based, at least in part, on amodified hypothesis resulting, at least in part, from the reception ofthe one or more modifications comprises: means for presenting one ormore advisories relating to the modified hypothesis. 158.-162.(canceled)
 163. The computationally-implemented system of claim 157,wherein said means for presenting one or more advisories relating to themodified hypothesis comprises: means for presenting at least one form ofthe modified hypothesis.
 164. The computationally-implemented system ofclaim 163, wherein said means for presenting at least one form of themodified hypothesis comprises: means for presenting an indication of arelationship between at least two event types as indicated by themodified hypothesis. 165.-166. (canceled)
 167. Thecomputationally-implemented system of claim 164, wherein said means forpresenting an indication of a relationship between at least two eventtypes as indicated by the modified hypothesis comprises: means forpresenting an indication of a relationship between at least a first typeof subjective user state and a second type of subjective user state asindicated by the modified hypothesis.
 168. Thecomputationally-implemented system of claim 164, wherein said means forpresenting an indication of a relationship between at least two eventtypes as indicated by the modified hypothesis comprises: means forpresenting an indication of a relationship between at least a type ofsubjective user state and a type of objective occurrence as indicated bythe modified hypothesis.
 169. The computationally-implemented system ofclaim 164, wherein said means for presenting an indication of arelationship between at least two event types as indicated by themodified hypothesis comprises: means for presenting an indication of arelationship between at least a type of subjective user state and a typeof subjective observation as indicated by the modified hypothesis. 170.(canceled)
 171. The computationally-implemented system of claim 164,wherein said means for presenting an indication of a relationshipbetween at least two event types as indicated by the modified hypothesiscomprises: means for presenting an indication of a relationship betweenat least a type of objective occurrence and a type of subjectiveobservation as indicated by the modified hypothesis.
 172. Thecomputationally-implemented system of claim 164, wherein said means forpresenting an indication of a relationship between at least two eventtypes as indicated by the modified hypothesis comprises: means forpresenting an indication of a relationship between at least a first typeof subjective observation and a second type of subjective observation asindicated by the modified hypothesis.
 173. Thecomputationally-implemented system of claim 157, wherein said means forpresenting one or more advisories relating to the modified hypothesiscomprises: means for presenting an advisory relating to a predication ofone or more future events based, at least in part, on the modifiedhypothesis. 174.-176. (canceled)
 177. The computationally-implementedsystem of claim 95, wherein said means for executing one or more actionsbased, at least in part, on a modified hypothesis resulting, at least inpart, from the reception of the one or more modifications comprises:means for prompting one or more devices to execute one or moreoperations based, at least in part, on the modified hypothesis.178.-180. (canceled)
 181. The computationally-implemented system ofclaim 177, wherein said means for prompting one or more devices toexecute one or more operations based, at least in part, on the modifiedhypothesis comprises: means for prompting one or more environmentaldevices to execute the one or more operations.
 182. Thecomputationally-implemented system of claim 177, wherein said means forprompting one or more devices to execute one or more operations based,at least in part, on the modified hypothesis comprises: means forprompting one or more household devices to execute the one or moreoperations.
 183. The computationally-implemented system of claim 177,wherein said means for prompting one or more devices to execute one ormore operations based, at least in part, on the modified hypothesiscomprises: means for prompting one or more sensing devices to executethe one or more operations.
 184. The computationally-implemented systemof claim 177, wherein said means for prompting one or more devices toexecute one or more operations based, at least in part, on the modifiedhypothesis comprises: means for prompting one or more network devices toexecute the one or more operations.
 185. (canceled)
 186. Thecomputationally-implemented system of claim 95, wherein said means forexecuting one or more actions based, at least in part, on a modifiedhypothesis resulting, at least in part, from the reception of the one ormore modifications comprises: means for executing the one or moreactions based on the modified hypothesis and in response to a reportedevent.
 187. The computationally-implemented system of claim 186, whereinsaid means for executing the one or more actions based on the modifiedhypothesis and in response to a reported event comprises: means forexecuting the one or more actions based on the modified hypothesis andin response to a reported event that at least substantially matches withone of at least two event types identified by the modified hypothesis.188. The computationally-implemented system of claim 187, wherein saidmeans for executing the one or more actions based on the modifiedhypothesis and in response to a reported event that at leastsubstantially matches with one of at least two event types identified bythe modified hypothesis comprises: means for executing the one or moreactions based on the modified hypothesis and in response to a reportedevent that matches with one of the at least two event types identifiedby the modified hypothesis. 189.-190. (canceled)